Blog

Optimizing Gherkin scenario step definitions

When writing test cases in Gherkin, the larger your set of scenario descriptions gets, the easier it is to create redundant step definitions.

Word order, using synonyms, all this leads to more and more step definitions to manage.

One tool to get an overview of redundancies is the following Python script. it search through a directory entered as a parameter and all its subdirectories, scans the files for step definitions and finally lists these with the file and line number alphabetically sorted in a text file.

Cypress: Finding and clicking a button in a table by checking the value of an input

The Problem:

We got a table with two columns and several rows. In column one, there is an input field for each row. In column two, there are two buttons per row. The buttons got the same name in all rows and no identification character in the HTML definition file besides its title (Edit or Delete).

Delete object in after hook via Rest

The Petclinic application is a demo implementation. This means there are some anomalies that real applications might not have. One such is the missing function of deleting an owner in the angular front end.

When testing the front end this leads to the anomaly, that the owner list grows until the rest server is reset and all previous data is lost.

A walk around is the use of the owners DELETE api from the Rest application server.