Cypress
Welcome, champion! 🔥
You've mastered 0 of 65 lessons. Start your first lesson free — no signup needed.
About this course
Cypress is one of the most popular tools for testing web apps in a real browser, and also one of the easiest to misuse. Tests that pass on one run and fail on the next, a cy.wait(5000) added to every spec, an attempt to await a Cypress command like a Promise: these come from misunderstanding how Cypress runs. Much of the advice online also uses APIs that newer versions have removed. This online Cypress course on Abekus teaches current Cypress properly, in short reading-card lessons each followed by an MCQ quiz.
Who this Cypress course is for
It is written for manual testers moving to automation, QA freshers and front-end developers who want reliable browser tests. You should know basic JavaScript and HTML; no test automation experience is needed. By the end you can write end-to-end and component tests, choose stable selectors, rely on retry-ability instead of fixed waits, control the network, cache logins, keep secrets out of specs and run suites in CI.
Examples follow one setup: Cypress 16.3.0 with JavaScript ES modules on Node.js 24 LTS, Chrome as the test browser, and configuration in cypress.config.js using defineConfig. Every lesson tests the same small to-do app, TaskBoard, running at http://localhost:3000, so selectors, stubs and sessions build on each other. Code blocks show Cypress code only and stay short. Removed APIs such as cy.server, cy.route, cy.exec and Cypress.env() appear only to show what replaced them. The course leaves out the Cypress app's UI panels, Cypress Cloud dashboards and paid features beyond a one-line mention, AI test features and visual-diff plugins.
How the lessons work
Each lesson is a short set of reading cards on one feature, usually with a short spec and what the run shows, followed by a quiz of multiple-choice questions. Many questions ask what a test will do, such as whether a command retries or which request an alias waits on. Lessons start with a first end-to-end test and how Cypress queues commands, then cover selecting elements, actions and assertions, retry-ability, values and aliases, custom commands, network control, test isolation, sessions and secrets, component testing and running in CI. You move at your own pace and earn a certificate when you finish.
MCQ practice vs video courses for Cypress
Video courses on Udemy, Coursera or YouTube suit learners who want to watch someone build a test suite in an editor. Many were recorded for older versions, though, and show APIs that Cypress 16 no longer has. This course is built for a different job: a short explanation followed straight away by questions about real specs, such as whether .click() retries, what cy.get yields inside .within(), why a variable set inside .then() is empty outside it, or which call reads a secret in Cypress 16. Cypress behaviour is precise, and predicting it question by question builds the mental model that ends flaky tests. Many testers use both.
Common Cypress mistakes
The course corrects these directly:
- Looking for cypress.json. Configuration has lived in cypress.config.js since version 10.
- Reading secrets with Cypress.env(). It was removed in 16; use cy.env(), or Cypress.expose() for public values.
- Seeding data with cy.exec(). It was removed in 16; use cy.task() or cy.request().
- Stubbing with cy.server() and cy.route(). They were removed in version 12; use cy.intercept().
- Writing const el = await cy.get(...). Commands are not Promises; use .then() or aliases.
- Expecting .click() to retry until it works. Only queries and assertions retry.
- Fixing flaky tests with cy.wait(5000). Wait on an aliased request or an assertion instead.
Best way to learn Cypress
Start with one short user journey and make it stable before adding more. A small suite that passes every time is worth more than a large one that people learn to rerun and ignore. Use data-cy attributes for selectors, let assertions do the waiting, stub the network where the backend is slow or unpredictable, and log in once with cy.session rather than through the form in every test. The final part of the course is built around these choices: Cypress against Playwright, end-to-end against component tests, a stubbed against a real backend, choosing what to test end to end, choosing UI login or cy.request login, and worked cases including a login flow with cy.session, a checkout flow with a stubbed payment API and a smoke suite on every pull request.