Page History
...
The configuration of @badeball/cypress-cucumber-preprocessor can either be done on a JSON file .cypress-cucumber-preprocessorrc.json or within package.json.
...
We need to have the cucumber-json-formatter tool, which can be downloaded from the respective GitHub repository. Make sure you pick the correct binary for your environment.
This tool is necessary to convert the Cucumber messages protobuf (*.ndjson file) report generated by @badeball/cypress-cucumber-preprocessor.
...
After being exported, the created .feature(s) will contain references to the Test issue key, eventually prefixed (e.g. "TEST_") depending on an Xray global setting, and the covered "requirement" issue key, if that's the case. The naming of these files is detailed in Export Cucumber Features backup.
| Code Block | ||||
|---|---|---|---|---|
| ||||
@REQ_CALC-7905 Feature: As a user, I can login the application #As a user, I can login the application @TEST_CALC-7903 Scenario Outline: Login With Invalid Credentials Should Fail Given browser is opened to login page When user "<username>" logs in with password "<password>" Then error page should be open Examples: | username | password | | invalid | mode | | demo | invalid | | invalid | invalid | | demo | mode | @TEST_CALC-7902 Scenario: Invalid Login Given browser is opened to login page When user "dummy" logs in with password "password" Then error page should be open @TEST_CALC-7901 Scenario: Valid Login Given browser is opened to login page When user "demo" logs in with password "mode" Then welcome page should be open |
...
After being exported, the created .feature(s) will contain references to the Test issue keys, eventually prefixed (e.g. "TEST_") depending on an Xray global setting, and the covered "requirement" issue key, if that's the case. The naming of these files is detailed in Export Cucumber Features backup.
| Code Block | ||
|---|---|---|
| ||
@REQ_CALC-7905 Feature: As a user, I can login the application #As a user, I can login the application @TEST_CALC-7903 @cypress/integration/login/login.feature Scenario Outline: Login With Invalid Credentials Should Fail Given browser is opened to login page When user "<username>" logs in with password "<password>" Then error page should be open Examples: | username | password | | invalid | mode | | demo | invalid | | invalid | invalid | | demo | mode | @TEST_CALC-7902 @cypress/integration/login/login.feature Scenario: Invalid Login Given browser is opened to login page When user "dummy" logs in with password "password" Then error page should be open @TEST_CALC-7901 @cypress/integration/login/login.feature Scenario: Valid Login Given browser is opened to login page When user "demo" logs in with password "mode" Then welcome page should be open(base) |
...