lecture 16 of 160 completed

Choosing tools, and knowing when Cypress is wrong

A senior engineer can name the cases where their favourite tool is the wrong answer.

What you'll learn

  • When Cypress is the wrong answer
  • How to compare tools without advocacy
  • How to make the case to a team

You will be asked to choose a tool, or to defend the one you have. The junior answer is to list features of the tool you know best. The senior answer starts with the constraints.

Let me be direct about where Cypress is a strong choice, and where it is not. Being able to say the second part is what makes people trust the first.

Cypress is a good fit when:

  • Your team writes JavaScript and will maintain the tests themselves.
  • You want an excellent debugging experience. The command log with time travel is still the best thing about Cypress, and it makes juniors productive quickly.
  • Your app is a normal web app in one tab.

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 →