lecture 1 of 160 completed

The architecture, and everything it costs you

Every Cypress limitation you will ever hit comes from one design decision. Learn the decision and you can predict the limits.

What you'll learn

  • Why Cypress runs inside the browser, and what follows
  • How to predict what the tool cannot do
  • How to answer that in an interview without defensiveness

Teams lose weeks to an SSO login test that cannot be made to work. Several engineers try. Someone suggests the tests are badly written.

Usually nothing is badly written. They are fighting the architecture, and nobody has explained it to them.

Senior work with any tool starts here: you should be able to predict what the tool cannot do, before you try it. For Cypress that prediction comes from one fact.

Cypress runs inside the browser, in the same window as your application.

Everything else follows. Read the consequences slowly, because each one explains a whole category of problem you will meet.

full course

Keep reading with the full course

The Foundations track and the first lessons in each framework are free. This lesson needs full course access. A course plan includes all lessons for Playwright, Cypress and Selenium.

See course plans →