QA Engineer

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

A test strategy defines what to test, how much of each type, and how testing integrates into the delivery process.

Systematic techniques for deriving test cases from requirements. The goal is maximum defect detection with minimum test cases.

Simultaneous learning, test design, and execution. The tester uses their knowledge of the system to discover behaviours that scripted tests miss.

Verifying that previously working functionality hasn't been broken by new changes. The primary value of an automated test suite — it prevents known-good behaviour from silently degrading.

The process a defect goes through from discovery to closure. A well-defined lifecycle ensures bugs don't get lost, misunderstood, or marked done before they're verified.

How quality practices integrate with DevOps pipelines. DevOps QA is not a team — it's quality gates, automated checks, and feedback loops embedded into the delivery pipeline.

↳ Quality in CI/CD pipelines

Prioritise testing effort toward areas of highest risk. You never have enough time to test everything — risk-based testing ensures the most critical and failure-prone areas get the most attention.

↳ Test what matters most — coverage that maps to business risk

How to get good test data reliably without coupling tests to each other or exposing production PII.

↳ Most test failures come from bad data, not bad tests

Testing how the system behaves under conditions, not just whether it does the right thing.

↳ Performance, security, reliability awareness

Finding bugs before they're written is cheaper than finding them after.

↳ Find defects before code exists — requirements and shift-left thinking