
This problem covers finding every control on a ticket office by the identity a person actually sees, and letting an assertion retry for a result that arrives late.
This problem covers narrowing a lookup to the card it belongs to, on a board where every stall repeats the same button and the same field labels.
This problem covers resolving a lookup that matches several elements, by the text beside it, by its position, and by an anchored match that tells apart two names where one contains the other.
This problem covers working a directory of repeated cards where every name appears at two heading levels, two beds are named so one contains the other, a control renders as either a button or a link, and a slow answer has to be waited for by retrying.
Learn to write production-style Cypress test suites through hands-on challenges, one concept at a time.
This path starts with how Cypress finds elements and retries for them. Each challenge gives you a small web app and asks you to write the tests for it, so you should be comfortable with basic JavaScript and with reading HTML. No earlier Cypress experience is needed. Locators come first because they decide whether your tests keep passing when the page changes.
1 module: Selectors & Retry-ability.
4 exercises, all easy.
Challenges run on Node.js 24.
No. Every challenge runs in a browser-based IDE with everything already set up, and your code is graded automatically against a test suite.