The method
You don’t learn to automate by watching someone else automate.
Most automation courses teach a tool. The problem is almost never the tool: it is knowing what to cover, at what level, and how to write test code that someone will still be maintaining three years from now.
- 01
A real framework
Pandora, the STRATEST automation framework.
Not a throwaway project built for the course and abandoned afterwards. You work on code that is used on client engagements, with its constraints and trade-offs. What you learn there — architecture, separation of concerns, data management — stays useful elsewhere, even if you never use Pandora again.
- 02
Real user stories
A business need written the way companies write them, gray areas included.
An exercise brief is clean: it says exactly what to do. A user story is not. It leaves questions open, its acceptance criteria are incomplete, and it is up to you to decide what needs to be covered. That decision is the core of the job — and it can’t be learned from exercises that come with answer keys.
- 03
A simulated QA team
You own your user stories, and you answer for them.
Each participant is given a scope they are responsible for. They design the test cases, automate them, and present their work to the group. Nobody fixes it for them. It is uncomfortable at first, and it is exactly the situation of starting a new job.
- 04
Four applications
Automated end to end, with real-world constraints.
Authentication, data shared between scenarios, asynchrony, elements that appear late. The four applications are chosen to cover the situations that break real suites — not the ones that make nice demos.
What we stand by
Your code is reviewed
It is the most effective learning mechanism, and the one every solo career change lacks. You don’t improve by looking at correct code: you improve when someone explains why yours will break in six months.
You learn to delete tests
A mature automation engineer deletes tests. It is a skill, and it means standing by a decision. Programs that only teach adding tests produce suites that grow until they are abandoned.
We don’t promise two weeks
Six to twelve months to work independently on an existing suite. Two to three years to design an architecture that holds up. Anyone who claims less is selling a certificate, not a skill.
The goal is for you to no longer need us
A training provider that creates dependency has a better business model. We prefer to pass on what we know: it is slower, and it is the only thing that lasts — for you as for the teams we support on client engagements.
Judge for yourself
9 full chapters of the learning path are free to access, no account needed. Whole chapters, not a trailer.