Testing Documentation
This section covers testing strategies, implementations, and best practices for the Fawkes platform.
Testing Strategy
Fawkes implements comprehensive testing at all levels to ensure platform reliability and quality.
- Test Automation Pattern - Testing best practices and patterns
Testing Types
Unit Testing
- Run unit tests with:
make test-unitorpytest tests/unit -v
Integration Testing
- Run integration tests with:
make test-integrationorpytest tests/integration -v
End-to-End Testing
- Run E2E tests with:
make test-e2e-all
BDD/Acceptance Testing
- Run BDD tests with:
make test-bddorbehave tests/bdd/features --tags=@local
User Experience Testing
Accessibility Testing
- Accessibility Testing Guide - How to test for accessibility
Usability Testing
- Usability Testing Guide - Conducting usability tests
Infrastructure Testing
Validation & Acceptance
Epic Validation
- AT-E1-006 Validation Coverage - Acceptance test coverage
Component Validation
- OpenTelemetry Validation - Telemetry validation
- Azure AKS Validation Checklist - AKS validation
Testing Commands
# Run all tests
make test-all
# Run specific test types
make test-unit # Unit tests
make test-integration # Integration tests
make test-bdd # BDD/acceptance tests
make test-e2e-all # All E2E tests
# Run specific validation tests
make validate-at-e1-001 # AKS cluster
make validate-at-e1-002 # GitOps/ArgoCD
make validate-at-e1-003 # Backstage
Related Documentation
- Development Guide - Development and testing setup
- How-To Guides - Step-by-step testing guides
- Troubleshooting - Common testing issues
- Runbooks - Operational testing procedures