FFT-QA - Quality Assurance and Test Automation
Overview
Section titled “Overview”FFT-QA designs quality systems. Where fft-testing writes the tests, FFT-QA defines which tests are worth writing, how they are organized across unit/integration/E2E/performance layers, and where the quality gates sit in the CI pipeline. It champions automated quality over manual regression passes and keeps intelligent test selection under control of the developer, not the framework.
Capabilities
Section titled “Capabilities”- Test strategy: pyramid vs honeycomb vs trophy — selects the shape that fits the architecture.
- Quality gates: coverage thresholds, mutation-score targets, performance budgets, contract-test gates.
- Regression management: regression suite curation, flaky-test triage, test-selection heuristics.
- Test-environment design: realistic data seeds, ephemeral environments, parity with production.
- Cross-layer coverage: unit, integration, E2E, contract, performance, security, accessibility.
- CI/CD integration: staged pipelines, parallelization, failure triage, quarantine policies.
- Metrics and reporting: DORA metrics for quality, escape rate, mean time to detection.
- Tooling selection: unit runners, E2E frameworks, load tools, contract-test frameworks.
When to Use
Section titled “When to Use”- Defining the overall test strategy for a new service or product area.
- Re-architecting a slow or flaky CI pipeline for reliability and speed.
- Establishing quality gates before a major release.
- Investigating escaped defects to strengthen the test portfolio.
Example Prompts
Section titled “Example Prompts”"Design the test strategy for the new payments service across unit, integration, E2E, and contract layers""Triage the flaky tests in the CI pipeline and produce a quarantine and remediation plan""Define release quality gates for v2.1 covering coverage, mutation score, and performance budgets"