mirror of
https://github.com/proffesor-for-testing/agentic-qe.git
synced 2026-09-19 08:45:47 +08:00
5380421f1e
- Corrected MCP server implementation status from 0% to 100% - Added details of 52 MCP tools across 8 categories - Updated overall progress from 46% to 54% (7/13 areas complete) - Added MCP server architecture details (357 lines server, 1836 lines tools, 60+ handlers) - Updated integration metrics: MCP Tools 52/50 (104% - exceeded target) - Removed MCP server from future work (already production-ready) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2.5 KiB
2.5 KiB
Claude Code Configuration
Project Overview
This project uses Agentic QE Fleet for comprehensive quality engineering.
🚀 AGENTIC QE FLEET - CRITICAL RULES
📦 Project Structure
The AQE implementation is in /agentic-qe/ subfolder by design:
- This is a modular monorepo pattern
- Core AQE system is separate from projects using it
- This allows:
- Centralized QE agent management
- Reusability across multiple projects
- Clean separation of concerns
- Easy updates and maintenance
🤖 Available QE Agents
- qe-test-generator: AI-powered test creation with property-based testing
- qe-test-executor: Parallel test execution with retry logic
- qe-coverage-analyzer: O(log n) coverage optimization with gap detection
- qe-quality-gate: Intelligent go/no-go decisions with risk assessment
- qe-performance-tester: Load testing and bottleneck detection
- qe-security-scanner: SAST/DAST integration with CVE monitoring
⚡ Agent Usage
Spawn agents via Claude Code Task tool:
Task("Generate tests", "Create comprehensive test suite", "qe-test-generator")
Task("Execute tests", "Run tests in parallel", "qe-test-executor")
Task("Analyze coverage", "Find coverage gaps", "qe-coverage-analyzer")
Or use MCP tools for coordination:
mcp__agentic_qe__fleet_init({ topology: "hierarchical" })
mcp__agentic_qe__test_generate({ framework: "jest", coverage: 0.95 })
🎯 Best Practices
- Initialize Fleet First: Run
aqe initbefore using agents - Use Parallel Execution: Spawn multiple agents in single messages
- Leverage Memory: Agents share state via Claude Flow memory
- Monitor Progress: Check agent status with
aqe status - Claude Flow Integration: Agents use hooks for coordination
⚠️ Common Pitfalls
- Don't expect agents in root .claude/agents/ - they're in project's .claude/agents/
- Real vs Mock:
aqe initcreates real agents (not mocked demos) - Hooks are intentional: Agents coordinate via Claude Flow hooks
- Memory is shared: All agents can access aqe/* memory keys
🔧 Commands
aqe init- Initialize AQE fleet in current projectaqe status- Show fleet statusaqe test <module>- Generate tests for a moduleaqe coverage- Analyze test coverageaqe quality- Run quality gate checkaqe agent spawn --name <agent>- Spawn specific agentaqe agent execute --name <agent> --task "<task>"- Execute task
Agentic QE Fleet - Enterprise-grade quality engineering powered by AI and sublinear algorithms