This Cucumber integration provides the capability to write and trace Cucumber feature files in Polarion and to collect the Test Records from the test execution.
Writing Feature Files
This extension includes a Gherkin Editor, which supports syntax validation. This editor can be added to the Work Item Form by adding this line to the Form Configuration:
<extension id="cucumber" label="Cucumber Test"/>
Afterward, the editor will show up in the Work Item form as follows:
The features written in this editor are added as attachments to the Work Item they were created in. The Test Cases are referenced in this Gherkin file using their ID as a tag (in this example “GURKE-987”). This way, you can define multiple scenarios in one feature file but still have one Test Case per scenario.
Accessing Gherkin Features
In addition to the availability of Gherkin Features in the attachments, there is also a REST API with multiple endpoints to access the feature files. There is a direct endpoint to access a specific feature and to upload and import Gherkin features. Furthermore, you can also use the Export API to get multiple feature files in a ZIP at once. Please consult the REST API documentation for further information.
Transferring Test Results to Polarion
This extension also adds multiple REST API endpoints to import Rest Results into Polarion. You can either send your results in Cucumber JSON or the JUnit format. In both cases, a new Test Run and a Test Record for every executed Test Case will be created and the status values will be set accordingly.
Further information about the use of this extension can be found in the Administration - the About tab of this extension. The REST API documentation is available in its tab.
If you have any questions, contact polarion-opensource@sbb.ch.