Good automated tests provide fast feedback loops and the confidence to refactor code, ultimately leading to better code written faster.
Abstracting test logic away from a specific framework like Cypress or Vitest reduces risk and allows you to use the best tool for each scenario.
Replace fragile CSS class selectors with semantic queries like `findByRole` to make tests resilient to styling changes and improve accessibility.
Abstracting UI interactions into a domain-specific language (DSL) makes tests more understandable for non-technical stakeholders and easier to maintain.
Approaching tests as specifications written before the implementation forces you to consider the public API from a user's perspective, leading to better design.
A practical demonstration shows how to write failing end-to-end and component tests first, then implement the feature to make them pass.
Frame TDD not as an overhead cost but as a crucial practice for keeping the long-term cost of change low and maintaining development velocity.
Structure your test files by domain, with drivers in a separate folder, and use TDD to design components that are less reliant on global state.
Hubert Burda Media
München, Germany
44:31Rob Richardson
54:23Ramona Schwering
31:21Markus Hatvan
44:40Alexander Lichter
54:44Marc Backes
56:49Jens Happe
30:55Alex Banul
1:00:10James Bender
Jobs that call for the skills explored in this talk.
Turboneer LLC
Mount Morris, United States of America
Adria Solutions ltd
Manchester, United Kingdom
epunkt GmbH
Amstetten, Austria
