Page History
...
Each .feature file will be processed as follows.
Tests:
- try to find the Test by key (in that project), if found then update it; else...
- try to find the Test having both
- a label with the original relative path of .feature (e.g. "core/sample_addition.feature)
- a label named "id:xxx", where xxx is some number (e.g. "id:1", "id:32"); this label comes from a scenario/scenario outline's tag
- try to find the Test having both
- a label with the original relative path of .feature (e.g. "core/sample_addition.feature)
- the same summary
- try to find the Test by summary (in that project), if found then update it; else...
- create Test in that project and add a label with the relative path of the feature, and another label corresponding to a tag "id:xxx" (if it exists)
Pre-Conditions:
- try to find the Pre-Condition by key (in that project), if found then update it; else...
- try to find the Pre-Condition having both
- a label with the original relative path of .feature (e.g. "core/sample_addition.feature)
- try to find the Pre-Condition by summary (in that project), if found then update it; else...
- create Pre-Condition in that
...
- project and add a label with the relative path of the feature
The mapping from the Scenario/Scenario Outline present in the .feature files to the Test issues in Jira would be as follows:
...