February 2015
Intermediate to advanced
338 pages
8h 16m
English
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:
| 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.
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—one that fails occasionally and at random. The same scenario, run on the same codebase in the same environment, ...