Deciding what to automate
Where do you start, and where not? The business case and the strategic choices.
Calculator: is it worth automating this test?
Enter your own numbers and see the break-even point instantly.
Is automating tests worth it? Do the math.
The formula, a worked example, and the rule of thumb.
Should I automate every test?
No. And precisely because we're fans of automation, we know why.
800 automated tests. Nobody looks at them.
Test automation isn't a goal in itself, it's a means.
The test pyramid isn't a law. It's a rule of thumb.
Three situations where deliberately deviating from the classic shape is the right call.
A suite you can trust
From red builds nobody looks at anymore to tests that actually mean something.
Test data is the neglected child of every test automation project.
The silent cause behind flaky tests and bugs nobody can reproduce.
What are flaky tests, and how do you fix them?
The problem isn't the failing test, it's that nobody looks anymore.
80% coverage. Does that let you sleep at night?
Coverage tells you what's covered, not whether your system works.
Technique and process
The layers you test, and when you test them.
Your UI can work perfectly while your API is broken
Postman/Bruno versus RestAssured, and what you should always check.
How many bugs do you still find after release?
Shift-left: building testing in from the start, not bolting it on at the end.
Who on your team owns the automated tests?
If the answer is "one person", that's a risk.
Accessibility testing isn't complicated. It just gets skipped a lot.
95.9% of the world's most-visited websites have at least one accessibility issue.
Less E2E. More confidence. Faster releases.
Consumer-driven contracts with Pact, how it works and when to use it.
A CI/CD pipeline without tests is a motorway without guardrails.
What a good pipeline needs, and why failing tests should always block the deploy.
Embedding testing in the organisation
Getting buy-in beyond the team, and winning the conversation with management.
