We’ve identified four main types of pain your team might start to feel if their Cucumber goes bad. Take a look and see whether you recognize any of these:
|Some of our tests fail randomly.||
|We keep breaking tests unintentionally.||
|Our features take too long to run.||
|Our stakeholders don’t read our features.||
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. Here’s our definition of a flickering scenario:
A flickering scenario fails occasionally ...