SDET

Central hub for all test automation and technical quality engineering knowledge. Every page in the Technical QA brain connects here.

Validating HTTP APIs at the integration layer — below the UI, above the database.

Advanced Playwright patterns beyond basic locators and clicks: custom fixtures, API testing, tracing, code generation, CI optimisation, and the Healer agent for self-healing selectors.

Validates that a system behaves acceptably under expected and peak load. Catches performance regressions before they become production incidents.

Structural patterns for maintainable automation code. Tests are code — they need design, abstraction, and refactoring the same as production code.

Automated checkpoints in a delivery pipeline that block promotion when quality thresholds aren't met. Quality gates make "definition of done" machine-enforceable rather than aspirational.

↳ Block broken code automatically

A test that sometimes passes and sometimes fails on the same code is a flaky test. Flaky tests erode trust in the test suite — engineers start re-running failures instead of investigating them.

Validates that two services (consumer and provider) can communicate correctly. Sits between unit tests and E2E integration tests.

↳ Schema validation between services — catch integration breaks early

Treating the test suite as a system to be monitored — tracking health, trends, and failure patterns over time.

↳ Read logs, metrics, and traces as a tester

The environments through which code travels from developer laptop to production. Environment gaps cause bugs that only appear in certain stages.

↳ Why tests pass in QA but fail in prod

Schema definition, custom validators, serialisation, and defensive data handling at system boundaries.

↳ Comparing large datasets and validating at scale