Test Automation Practice
Write end-to-end browser tests the way QA engineers do. Each challenge gives you a small web app and asks you to write its tests, in Cypress, in Playwright with TypeScript, or in Selenium 4 with Java. Every path starts with locators and waiting, because they decide whether your tests keep passing when the page changes. On every challenge you choose whether to work with AI agents, AI chat only, or no AI.
Test Automation
3 pathsFrequently asked questions
7Which paths are in this category?
3 paths: Cypress (4 challenges), Playwright TypeScript (4 challenges) and Selenium Java (4 challenges).
How many challenges are there?
12 challenges across 3 modules.
Do I need to install anything?
No. Every challenge runs in a browser-based IDE with everything already set up, and your code is graded automatically against a test suite.
Which tool should I pick?
It depends on the language you’re comfortable with. Cypress needs basic JavaScript, Playwright needs basic JavaScript or TypeScript, and Selenium needs you to be able to write a small Java program. All three expect you to read HTML, and none needs earlier experience with the tool.
What do the challenges ask me to do?
Each one gives you a small web app or page and asks you to write the tests for it, so you practise testing a real interface, not toy examples.
Why does every path start with locators?
Finding elements reliably, and waiting for them, is what every later test depends on. Weak locators are the main reason end-to-end tests break when a page changes.
Can I use AI while I solve a challenge?
Yes, if you want to. Each challenge lets you choose how to work: with AI agents, with AI chat only, or with no AI at all.
