How Gherkin specifications make our projects more precise and more testable
Why do we work with Gherkin specifications at Cap3?
In many projects, the central challenge lies less in technical implementation than in the precise coordination of what is to be created professionally and functionally. Different roles in the team often interpret requirements differently. By jointly developing an example-based specification (“specification-by-example”), we at Cap3 create an interdisciplinary understanding — from project management to development to testing. In this way, we ensure that functionalities have already been comprehensively considered before implementation.
An example-based specification is a collaborative approach to software development: Requirements are not described abstractly, but defined using concrete, realistic scenarios. In order to record these in a structured manner and process them further automatically, a fixed sentence scheme is required. At Cap3, we often use the Gherkin notation for this, as it translates requirements into easy-to-understand scenarios.
How Gherkin scenarios work
The description language Gherkin provides the following structure for a scenario that describes the specific behavior of an application and is deliberately kept simple:
- Given describes the initial situation of the scenario
- When describes the action that is performed by users
- Then describes the expected result or response of the system
- And resp But is used in conjunction with other keywords to supplement them
This clarity reduces scope for interpretation, creates commitment and ensures more precise implementations.
Example scenario
SCENARIO: Saving the start information
The start details should be saved so that they only have to be entered once.
GIVEN The user has entered the start details when using the app before
AND The app hasn't been reset or reinstalled since
WHEN the user opens the app
THEN Is the user not asked to enter the start information
AND she sees her personalized start screen.
From example mapping to example-based specification with Gherkin
At Cap3, we use Example Mapping as a precursor to example-based specification with Gherkin and as a central communication format between project management, development, design and testing. In joint sessions — often in the spirit of”Three Amigos“— team members from the respective areas contribute their perspective. The rules, examples and open questions developed there are then incorporated directly into specific example-based scenarios.
This creates a consistent red thread:
- Example mapping makes requirements understandable.
- Developing an example-based specification with Gherkin results in a precise, testable scenario.
- The same basis is used from idea to release.
This creates a structure that not only speeds up implementation, but also increases the quality of the final software.
Use in our own CAP3 web-based testing tool
In a previous blog article we have already presented our own web-based tool for optimizing software testing. Gherkin scenarios form the ideal basis for a structured, testable test design — and our tool supports exactly this approach.
The integration of Gherkin specification and tool support creates a consistent testing process:
- Scenarios can be adopted directly
- Test cases are uniformly documented
- Tests are easier to overview and prioritize
- Professional quality is more visible
This not only makes testing more efficient, but also much more comprehensible for all project participants.
Conclusion: More clarity, better quality, faster progress
Gherkin specifications are a central element of how we work at Cap3. They combine project management, development, and testing in a way that is understandable, accurate, and efficient. In combination with our own testing tool, the result is a continuous process that sustainably strengthens the quality of our digital solutions.
sources:
Cucumber.io/docs/bdd/who-does-what/ #the -three-amigos
.png)
