What We Just Learned
Working with legacy code is always a challenge, but you can use Cucumber scenarios to help make it a much more enjoyable challenge. Be pragmatic! Don’t exhaust yourself trying to retrofit a complete set of Cucumber features for everything the system already does. Instead, add them gradually, one at a time, as you need them.
You’ll use characterization tests to help understand what the system is already doing and to give you some security before you make a change. Similarly, every time you discover a bug, you’ll trap it with a new Cucumber scenario. And, every time you add new behavior to the system, start by describing it with a Cucumber feature.
Code coverage can give you and your team feedback and encouragement about ...
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.
Read now
Unlock full access