O'Reilly logo

The Cucumber for Java Book by Seb Rose, Matt Wynne, Aslak Hellesoy

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

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:

SymptomProblem
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—one that fails occasionally and at random. The same scenario, run on the same codebase in the same environment, ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required