It's a (Testing) Trap! - Common Testing Pitfalls and How to Solve Them

Ramona Schwering
Ramona Schwering

June 8, 2021

This content is also available in german

“It’s a trap” - a call or feeling we all might be familiar with, not only when it comes to Star Wars.
FrontendTestFest'21
MOONCOM'21
TestJS Summit'21
VueJS Amsterdam'22
EnterJS'22
Developer Week'22

Abstract

“It’s a trap” - a call or feeling we all might be familiar with, not only when it comes to Star Wars. It’s signalizing a sudden moment of noticing imminent danger. This situation is a nice allegory for an unpleasant realization in testing. Imagine having the best intentions when it comes to testing, but still ending up with tests failing to deliver you any value at all? Tests who are feeling like a pain to deal with?

When writing frontend tests, there are lots of pitfalls on the way. In sum, they can lead to bad maintainability, slow execution time, and - in the worst-case - tests you cannot trust. But it doesn’t have to be that way. In this session, I will talk about the common mistakes developers make, at least from my experience. And of course, on how to avoid them. Testing doesn’t need to be painful, after all.

Slides

Recording