This directory contains comprehensive testing documentation for the AI Development Agent system.
The testing strategy follows test-driven development principles with comprehensive coverage across all system components and layers.
- Unit Testing - Component-level testing for individual functions and classes
- Integration Testing - Testing component interactions and API endpoints
- System Testing - End-to-end testing of complete workflows
- Performance Testing - Load testing and performance validation
- Security Testing - Security vulnerability and compliance testing
- Test Fixtures - Shared test data and setup utilities
- Mocking Guide - Mock objects and test isolation strategies
- Test Development Plan - LangGraph-specific testing approaches
See Test Organization Rules for detailed guidelines on:
- Test file structure and naming
- Test category organization
- Code coverage requirements
- Testing best practices
The Test Suite Summary provides:
- Current test coverage metrics
- Test execution status
- Performance benchmarks
- Quality gates and validation
- pytest - Main testing framework
- pytest-cov - Coverage reporting
- pytest-asyncio - Async testing support
- unittest.mock - Mocking framework
- LangSmith - LLM agent testing and tracing
- httpx - HTTP client testing
- Streamlit testing - UI component testing
- Database testing - Transaction isolation and cleanup
# Run all tests
pytest
# Run specific test categories
pytest tests/unit/
pytest tests/integration/
pytest tests/system/
# Run with coverage
pytest --cov=src tests/
# Run performance tests
pytest tests/performance/- All tests run automatically on git push (via pre-push hooks)
- Coverage reports generated and tracked
- Performance regression detection
- Security vulnerability scanning
Tests must pass the following quality gates:
- Unit Test Coverage: Minimum 80%
- Integration Test Coverage: Minimum 60%
- Critical Path Coverage: 100%
- Performance Benchmarks: Within acceptable thresholds
- Security Scans: No high-severity vulnerabilities
- Test-Driven Development: Write tests before implementing features
- Isolated Testing: Tests must not depend on external services
- Deterministic Tests: No false positives or flaky tests
- Clear Assertions: Tests assert real working, productive code
- Comprehensive Coverage: Test normal, edge, and error cases
- Development Standards - Code quality and development practices
- Implementation Guides - Feature implementation strategies
- Architecture Documentation - System design and components
- LangGraph Testing - Agent workflow testing approaches
For questions about testing practices or to contribute to testing documentation, see the project's main documentation index.