A worked reference for test automation
Test automation, written down properly and linked together.
83 articles across 11 sections: the levels of testing and what belongs at each one, the tools that run them, the pipelines that run the tools, and the practices that decide whether any of it survives contact with a real codebase. Samples in TypeScript, C#, Java and Python, and no page that ends where the interesting part starts.
If you only read six
- The Testing Pyramidhow much of each kind of test to write
- Flaky Teststhe failure mode that kills suites
- Playwrightthe default browser tool in 2026
- Test Doublesmock, stub, fake, spy — precisely
- Testing in GitHub Actionsrunning all of it on every push
- SDET vs Automation Tester vs Manual QAwho does what, and why it matters
The whole map
Nothing here is behind a click you have to guess at. Every section, and everything in it.
Levels of Testing
What each level can prove, and what it costsPractices & Patterns
The disciplines that decide whether a suite is trustedTools & Frameworks
Runners, drivers, mocking libraries and fakesUI Framework Testing
React, Angular, Vue, Knockout and the DOM underneathPlatforms
Browsers, desktop, mobile, Flutter, Avalonia, APIsLanguages
TypeScript, C#, Java, Python — the same ideas, four dialectsBeyond Functional
Performance, data, security, access, accessibilityCoverage
What the percentage means, and what it does notCI/CD Pipelines
Running all of it, on every pushEvidence & Diagnostics
Making a CI failure diagnosableRoles & Strategy
Who does what, and what to automate at allRecently updated
- Accessibility Testing19 September 2026
- Android App Testing19 September 2026
- API Testing19 September 2026
- Appium19 September 2026
- Arrange-Act-Assert19 September 2026
- Authorization Testing19 September 2026
How End To End Tester is built
Next.js, server-rendered, CQRS and event sourcing underneath — the same architecture as the other applications in this family, so the examples about testing an evented system are drawn from the site you are reading. Tools are coming; the writing came first.
Every article has a runnable sample — working tests rather than fragments, in TypeScript, C#, Java, Python, Ruby and Dart, running in CI on every push.
More about the site