Page History
...
The tutorial assumes using Xray as master; however, you can edit your .feature and .meta files outside of Jira (eventually storing them in you VCS using Git, for example) - more on that on the final section.
Using Jira and Xray as master
The first step is to create a Cucumber Test, of Cucumber Type "Scenario", in Jira. The specification would be exactly the same as the one provided in the original repository.
After creating the Test in Jira and associating it with requirements, etc., you can export the specification of the test to a Cucumber .feature file via the REST API, or the Export to Cucumber UI action from within the Test/Test Execution issue or even based on an existing saved filter. A plugin for your CI tool of choice can be used to ease this task.
The coverage and the test results can be tracked in the "requirement" side (e.g. user story).
After being exported, the created file will be similar to the original , but will contain the references to the Test issue key and the covered requirement issue key.
...
| Code Block | ||
|---|---|---|
| ||
@REQ_CALC-4805
Feature: Google search (gwen-web-demo)
@TEST_CALC-4823 @1_CALC-4805.feature @features/1_CALC-4805.feature @features/google/Google.feature @id:1
Scenario: Perform a google search
Given I have Google in my browser
When I do a search for "Gwen automation"
Then the first result should open a Gwen page |
...
| Info | ||
|---|---|---|
| ||
Please see Testing in BDD with Gherkin based frameworks (e.g. Cucumber) for an overview of the possible workflows. |
Using Git or other VCS as master
...
| Code Block | ||
|---|---|---|
| ||
Given I have Google in my browser When I do a search for "Gwen automation" Then the first result should open a Gwen page |
...