Gherkin-Based Feature Files
- APPWRK Writer
- Noopur Varshney [AIO Tests]
AIO Tests allows you to import feature files from your system with ease. While importing a gherkin-based feature file:
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.
In this documentation, you’ll understand:
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 2: On the Cases tab, click on the Import Cases button.
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
Step 4: Once you upload the file, the Import Configuration section will appear on the screen. On the Import Configuration page, you will get two options- Folder and Default Status.
Folder: Default folder where scenarios will be imported as tests. Select the folder from the already created folders drop-down.
By default, the Not Assigned folder is selected but the user can select from the already created folders via the drop-down.
Default Status for Newly Created Cases: Status in which to import scenarios. Select the Default Status for newly created cases from the Status drop-down menu.
Required Fields: For case creation and update, there are some mandatory fields that users need to fill out. These mandatory fields will be populated under the Required Fields. Users need to enter the required details in the respective fields.
Users have the option to update the fields of existing cases for mandatory fields by selecting the Yes option from the dropdown list against the Update fields for existing cases field.
Step 5: Click on the Start Import button to create one batch job for each selected file.
Once you click on the Start Import button, you will be redirected to the Jobs section, and a success message will be displayed on the screen stating, “Batch <batch #> created successfully.”
Job: The Job tab shows all the import requests that have either been submitted or completed. Once the batch is created, it shows the status “Queued”. The import function is a batch process that runs every 2 minutes and checks if any files have been submitted/queued for import. If new files exist, they are processed. Clicking the Refresh button below will update the status of the batch to either “Running” or “Completed”.
Upon clicking the down-carat icon next to the Created Date, the result of the batch processing will be displayed on the screen along with errors if any.
For further queries and suggestions, feel free to reach out to our customer support service via help@aiotests.com.