Feeling the Pain
We’ve identified four main types of pain that your team might start to feel if their Cucumber goes bad. Take a look and see whether you recognize any of these:
| Symptom | Problem |
|---|---|
| Some of our tests fail randomly. |
Flickering scenarios |
| We keep breaking tests unintentionally. |
Brittle features |
| Our features take too long to run. |
Slow features |
| Our stakeholders don’t read our features. |
Bored stakeholders |
Let’s take a closer look at each of these symptoms.
Flickering Scenarios
When a scenario that was passing yesterday is failing today, with the same source code running in the same environment, you have what we call a flickering scenario. Here’s our definition of a flickering scenario:
- Flickering scenario
-
A flickering scenario fails ...
Get The Cucumber Book now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
