Skip to Main Content
The Cucumber for Java Book
book

The Cucumber for Java Book

by Seb Rose, Matt Wynne, Aslak Hellesoy
February 2015
Intermediate to advanced content levelIntermediate to advanced
338 pages
8h 16m
English
Pragmatic Bookshelf
Content preview from The Cucumber for Java Book

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, ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

BDD with JUnit 5 and Cucumber demo

BDD with JUnit 5 and Cucumber demo

Cătălin Tudose
Testing Java Microservices

Testing Java Microservices

Andy Gumbrecht, Jason Porter, Alex Soto
Design Patterns and Best Practices in Java

Design Patterns and Best Practices in Java

Kamalmeet Singh, Adrian Ianculescu, Lucian-Paul Torje
Java Concurrency in Practice

Java Concurrency in Practice

Brian Goetz, Tim Peierls, Joshua Bloch, Joseph Bowbeer, David Holmes, Doug Lea

Publisher Resources

ISBN: 9781680500677Errata Page