QA Brain

Central hub for all quality assurance knowledge. Every page in the QA brain connects here.

---

Strategy and Planning

qa/test-strategy · qa/risk-based-testing · qa/qa-metrics · qa/non-functional-testing · qa/test-planning · qa/shift-left-testing · qa/qa-leadership

Test Design

qa/test-case-design · qa/bdd-gherkin · qa/exploratory-testing · qa/test-documentation

Defect Management

qa/bug-lifecycle · qa/root-cause-analysis · qa/negative-testing

Process and Agile

qa/agile-qa · qa/qa-in-devops · qa/regression-testing · qa/test-reporting · qa/pair-testing

Specialist Testing

qa/accessibility-testing · qa/mobile-testing · qa/cross-browser-testing · qa/security-testing-qa · qa/international-testing · qa/end-to-end-testing

Test Infrastructure

qa/test-environments · qa/test-data-management

Tools and Acceptance

qa/qa-tools · qa/uat

Automation and Strategy

qa/test-automation-strategy · qa/smoke-sanity-testing · qa/continuous-testing · qa/automation-debt · qa/risk-based-test-selection

Defect Prevention and Quality

qa/defect-prevention · qa/ai-testing · qa/compliance-testing · qa/defect-clustering

Release Governance

qa/release-sign-off

Production Quality

qa/production-monitoring-qa

Extended Testing

qa/usability-testing · qa/performance-testing-qa

QA Consulting and Process Improvement

qa/benefits-realisation · qa/qa-change-management · qa/test-estimation · qa/uat-governance

Reporting and Communication

qa/performance-test-reporting · synthesis/technical-communication

Connections

• qa/process-improvement-model — the consulting methodology that frames many of the QA practices indexed here
• qa/benefits-realisation — outcome measurement layer that connects QA practice improvement to business value
• qa/qa-change-management — the people-side discipline that determines whether practices in this hub are actually adopted
• synthesis/technical-communication — cross-domain communication skills applied to QA reporting and stakeholder briefing

Open Questions

• What testing scenarios does this technique systematically miss?
• How does this approach need to change when delivery cadence moves to continuous deployment?