• Skip to main content
Super Early Bird - Save 30% | Teams save up to 25%

AutomationSTAR

Test Automation Conference Europe

  • Programme
    • AutomationSTAR Team
    • 2025 programme
  • Attend
    • Why Attend
    • Volunteer
    • Location
    • Get approval
    • Bring your Team
    • 2025 Gallery
    • Testimonials
    • Community Hub
  • Exhibit
    • Partner Opportunities
    • Download EXPO Brochure
  • About Us
    • FAQ
    • Blog
    • Test Automation Patterns Wiki
    • Code of Conduct
    • Contact Us
  • Tickets

Track Talk DD5

Diagnosis and Treatment of Cucumber Diseases

Roland Germ

Katrin Heiderer

12:00-14:45 Thursday 10th October

Please note this is a 90 minute Deep Dive, with a break during the session.

The implementation of steps in Cucumber can be considered as declarative or imperative style. The description of test scenarios in Gherkin is a declarative approach to writing tests, where the tests are described in natural language. The actual implementation of steps in a programming language is done in an imperative style and can be considered as procedural programming, as the steps are executed in a specific order to achieve the desired test results. However, it also allows for a higher level of abstraction through the use of Gherkin, which makes it not exactly comparable to traditional procedural approaches.

Kent Beck and Martin Fowler have coined the term “code smell” to explain certain patterns in the source code that indicate potential problems or opportunities for improvement. In the context of Behavior-Driven Development (BDD) tools such as Cucumber, SpecFlow, and Reqnroll, unique code smells, which we will refer to as ‘cucumber diseases,’ can arise due to the distinct nature of writing and maintaining tests in a BDD framework.

In this workshop, we’ll:

  • diagnose these cucumber diseases by examining their symptoms and understanding their impact
  • explore treatments and
  • focus on refactoring techniques that can address these issues.

Participants will engage in hands-on prepared coding exercises in either Cucumber or Reqnroll, applying these treatments to a prepared test suite. Addressing these ‘cucumber diseases’ involves applying best practices such as maintaining clear and concise scenarios, reusing step definitions appropriately, ensuring steps are user-focused, and fostering consistent terminology. By recognizing and addressing these BDD-specific code smells, teams can improve the effectiveness and maintainability of their BDD test suites, leading to better software quality and more efficient development processes.

Requirements

  • Laptop
  • GitHub account
  • Browser or IDE/Editor (e.g., VS Code, IntelliJ IDEA) with Git integration and your preferred BDD tool
  • Experience either with Java and Cucumber, or C# and Reqnroll or SpecFlow
BACK TO PROGRAMME

What you will Learn

  1. Appreciate both clear descriptions in Gherkin and the practical implementation in the programming language.
  2. How certain patterns in the Gherkin code and in the step implementations can indicate potential problems or opportunities for improvement and refactoring.
  3. Practise directly applying the concepts you have learnt in examples and how you can treat the identified "cucumber diseases" through targeted refactoring

Session Details

  • Advanced
  • 90 mins
  • Hands-on Workshop
Buy Conference Ticket

Session Speaker

Roland Germ

Technical Agile Coach - Nagarro, Austria

As a technical agile coach, Roland Germ helps software development teams improve their collaboration and technical excellence to develop more effectively and reduce their technical debt. He has more than twenty years of experience in software development and has been involved in software craftmanship and agile practices for the software developer since 2005. He leads communities with coding workshops both internally at Nagarro and for customers on topics such as Clean Code and Test Driven Development (TDD). In addition, he regularly holds training courses on TDD and agile software development.

Co Speaker

Katrin Heiderer

Technical Agile Coach - Nagarro, Austria

Working in software development for multiple years, I can relate to the struggles and pains most developers have. As Technical Agile Coach, I coach teams get better at programming practices, Continuous Integration and Development, Clean Code, BDD and many other technical practices (Mob programming, refactoring of legacy code, ...). I try to help organizations who struggle with major technical debts, the pain of refactoring legacy code and maintaining it and try to find a tailored solutions for each problem.

Stay in the Loop

Never miss important announcements, updates, and special offers from AutomationSTAR.

.

"*" indicates required fields

Send me more Information

Name*
GDPR*

Copyright © 2026 · Impressum · Privacy · T&C

part of the