...
Each scenario/scenario outline gets mapped to one AIO Test case. If the test case already exists in AIO, the case will be updated based on the feature file.
Scenario outline gets converted into a single case and example values become datasets/examples.
For adding a story as a requirement in the newly created case, the scenario or the feature needs to be annotated with @JREQ-<Storykey>
Docstrings and Data tables get copied into the data column.
| Table of Contents |
|---|
Scenario to AIO Tests Mapping
The table given below shows how data from a feature file maps to a newly created case in AIO Tests.
Scenario | AIO Test Case | Note |
Scenario Name | Title |
|
Feature name | Description |
|
Case Key | AIO Test case key | If the specified key exists in AIO, the case will be updated with changes in feature file. |
Steps | Steps |
|
Data Table in Steps | Data in steps |
|
Docstrings in Steps | Data in steps |
|
Tags | All tags get added to case |
|
Requirement id | Jira Requirements [if at feature level then, all tests created from scenarios will have mapping] | All requirements need to be prefixed with JREQ- |
Background Steps | Steps in case - before the scenario steps |
|
Rule | Description |
|
Examples | Example |
|
Steps to Import Feature File
Step 1: To import a feature file, simply click on the Cases option in the top bar menu.
...
Step 3: On the import cases page, you will get 3 tabs- File, Other Projects, and Jobs. On the File page, click on the “Browse to upload file” button under the Feature File box to import a .feature file.
Sample Feature Files
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
...