Theory doesn't make developers
think about quality differently.
Practical, applied QA training for engineering teams — structured around real codebases, real risk, and the decisions your team makes every day. Half-day sessions or a series of three.
Generic training
produces generic results.
Most QA training covers concepts. What risk-based testing is, how the testing pyramid works, what a test case should contain. Engineers come away having heard those concepts — and go back to testing the same way they did before.
These workshops are different in two ways. First, they're applied to your team's actual context — your product, your stack, your release process. The exercises use real scenarios, not synthetic examples. Second, they're honest about the gap between QA theory and what actually works in a small engineering team without a dedicated QA function.
The goal is a team that makes better decisions about what to test, how to write tests that stay useful, and when to escalate a quality concern — not a team that passed a certification exam.
Four topics. Mix-and-match or series of three.
Risk-based testing
How to identify what actually matters to test, how to score and prioritise risk, and how to make the coverage vs. time trade-off explicit rather than implicit. Practical application to a real product area.
Test automation fundamentals
What makes a test suite maintainable vs. a liability. Writing tests that fail for the right reasons. The difference between testing behaviour and testing implementation. Applied to your team's stack.
AI-assisted testing in practice
How to use AI tools to accelerate test case creation, augment coverage, and reduce maintenance overhead — without losing the judgment that makes testing valuable. Hands-on with Playwright AI and AI-assisted approaches.
Quality ownership for developers
For teams without a dedicated QA function. How to build quality thinking into development practice — definition of done, code review checklists, how to write a bug report that gets fixed, and when to escalate.
Half-day. Or a series of three
over two to three weeks.
Single topic
3–3.5 hours. One topic from the list above. Pre-session questionnaire to tailor content to your team. Exercises applied to your actual codebase or product area. Post-session reference document.
Three topics
Three half-day sessions over 2–3 weeks. Topics chosen from the four options. Sequenced to build on each other. Better value; continuity between sessions lets the team apply learning before the next one.
Tailored to your team
All sessions are customised — not delivered from a slide deck designed for a generic audience. Pre-session review of your product, stack, and team context shapes the content and exercises.
✓ Junior engineers who need QA foundations
✓ Teams adopting test automation for the first time
✓ Mixed-ability teams — workshops calibrated to the group
✓ 4–12 attendees (can accommodate larger groups)
Fixed-price. Better value as a series.
All sessions include: pre-session questionnaire, content tailored to your team, post-session reference document, and follow-up email Q&A window of 7 days. Delivered remotely (or in-person for UK locations — travel costs extra).