Requirements traceability in Cucumber
A user survey
BDD | Posted September 14, 2020

Overview

Cucumber is an open source tool that provides the ability to create automated test scripts and specifications that are business readable.

Over the years, we’ve received many enquiries from Cucumber users about traceability  – which we’ve answered as best we can. The time has come to find out if there’s any way we can support traceability within the Cucumber eco-system. To do that we need to understand what sort of traceability our users are looking for… and why.

If you're willing to help us understand your requirements traceability needs,
please sign up here
to schedule a short online conversation.

What we’re asking for

We would like to arrange a 30-minute video call to understand how your organisation currently satisfies its needs for traceability – or not.

We’re interested in talking to a wide range of people (developers, testers, POs, managers, PMO, CxO etc.), whether your need for traceability is external (compliance/regulatory) or internal (risk/quality) or both.

Our only strict criteria is that your organisation currently uses some version of Cucumber (including SpecFlow, Behat and others).

Why you should participate

In return for helping us explore the demand for traceability within the Cucumber community, you will get a chance to influence our direction. Additionally, we’ll be able to offer you and your teams early access to any features that we develop in this space. And we’ll share an anonymised summary of our research with you when we’re done.

If you're willing to help us understand your requirements traceability needs,
please sign up here
to schedule a short online conversation.

Who we are

We’re the creators and maintainers of the Cucumber open source software (Ruby/Java/JavaScript). We work closely with the teams that maintain versions of Cucumber for other languages.