Skip to main content
Glama
02-strategy.mdβ€’4.36 kB
# Test Strategy & Priority Framework > **Context:** Comprehensive testing methodology with priority-based execution approach > **Prerequisites:** [Overview](./01-overview.md) - Understanding of testing objectives and scope > **Next Steps:** [Execution Process](./03-execution.md) or [Test Cases](./04-test-cases/) ## Test Strategy This document outlines the systematic approach for testing the Attio MCP Server using a priority-based framework with quality gates to ensure efficient validation and clear go/no-go decisions. ### Priority Framework Tests are organized in three priority levels with specific success criteria: | Priority | Tools | Success Rate | Duration | Quality Gate | |----------|-------|--------------|----------|-------------| | **P0 - Core** ⚑ | CRUD operations | 100% (5/5) | 2 hours | MANDATORY | | **P1 - Essential** πŸ”§ | Attributes, advanced search | 80% (3/4) | 2 hours | PRODUCTION GATE | | **P2 - Advanced** πŸš€ | Relationships, batch ops | 50% (3/5) | 2 hours | ENHANCEMENT | #### Quality Gates Decision Matrix **Quality Gates:** - **P0 failure** = STOP testing (system not ready) - **P1 <80%** = Evaluate production readiness - **P2 <50%** = Document but don't block release ### Priority Level Definitions #### Priority 0 (P0) - Core Foundation ⚑ **Critical Success Factor:** MANDATORY **Success Criteria:** 100% of P0 tests must PASS (5/5) **Duration:** Maximum 2 hours **Tools Covered:** - Search Records (basic functionality) - Get Record Details (data retrieval) - Create Records (data creation) - Update Records (data modification) - Delete Records (data removal) **Decision Point:** If P0 fails, STOP - system not ready for testing #### Priority 1 (P1) - Essential Extensions πŸ”§ **Critical Success Factor:** PRODUCTION GATE **Success Criteria:** Minimum 80% pass rate (3/4 tests) **Duration:** Maximum 2 hours **Tools Covered:** - Get Attributes (schema discovery) - Discover Attributes (dynamic exploration) - Get Detailed Info (specific data types) - Advanced Search (complex filtering) **Decision Point:** If <80% pass rate, evaluate production readiness #### Priority 2 (P2) - Advanced Features πŸš€ **Critical Success Factor:** ENHANCEMENT **Success Criteria:** Minimum 50% pass rate (3/5 tests) **Duration:** Maximum 2 hours **Tools Covered:** - Search by Relationship (connected data) - Search by Content (content-based queries) - Search by Timeframe (temporal filtering) - Batch Operations (bulk processing) - Batch Search (parallel queries) **Decision Point:** Nice-to-have features, don't block release ### Testing Phases #### Phase 1: Functional Testing - **Executor:** Technical agent (familiar with system architecture) - **Focus:** Core functionality validation and technical correctness - **Duration:** 6 hours maximum (2 hours per priority level) - **Objective:** Validate that all tools work as designed and handle expected scenarios **Execution Order:** 1. **Setup Phase** (30 minutes): Prepare test data, verify environment 2. **P0 Core Testing** (2 hours): Must achieve 100% pass rate 3. **P1 Essential Testing** (2 hours): Target 80% pass rate 4. **P2 Advanced Testing** (1.5 hours): Target 50% pass rate #### Phase 2: Usability Testing - **Executor:** Fresh agent (unfamiliar with system - simulates new user) - **Focus:** Documentation clarity, parameter understanding, and user experience - **Duration:** 2-3 hours estimated - **Objective:** Identify documentation gaps and parameter confusion that could affect real users **Focus Areas:** - Parameter clarity and intuitive naming - Error message helpfulness and actionability - Documentation completeness and accuracy - Edge case handling and graceful degradation ### Success Metrics Summary | Phase | Executor | Duration | Success Criteria | Quality Gate | |-------|----------|----------|------------------|-------------| | **Phase 1** | Technical Agent | 6 hours | P0: 100%, P1: 80%, P2: 50% | Production Readiness | | **Phase 2** | Fresh Agent | 2-3 hours | Clear documentation, intuitive usage | User Experience | --- **Related Documentation:** - [Previous: Overview & Objectives](./01-overview.md) - [Next: Execution Process & Workflow](./03-execution.md) - [Reference: Test Cases Details](./04-test-cases/) - [Reference: Quality Gates & Decision Criteria](./05-quality-gates.md)

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kesslerio/attio-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server