AIO Tests allows you to export BDD/Gherkin-based tests into feature files with ease. By exporting BDD cases to feature files, you can not only review the test cases offline but also share them with others who do not have access to test cases.
| Table of Contents |
|---|
Why You Should Export BDD Cases to Feature File
On AIO Tests, users can export the BDD/Gherkin-based tests to feature files in an organized way as per their requirements to access the up-to-date test case details offline. Here are some of the reasons why you should export the BDD cases to the feature file.
...
Offline review of test reports: By exporting BDD cases to feature files, testers can review test reports offline. It provides testers flexibility to work independently in situations where internet connectivity is poor or unreliable.
...
Share with unauthorized users: Exporting and downloading BDD cases to feature files enables testers to share test reports with stakeholders who do not have access to AIO Tests. It not only expands the reach to share testing insights with a broader audience but also fosters better communication with team members who may not be involved in the testing process.
...
Transfer test files across different systems: One of the major benefits of exporting BDD cases to feature files is that it allows you to transfer your test case information to your new device without risking data loss.
...
use them directly as a source for writing step definitions in Cucumber or SpecFlow.
In this documentation, you’ll understand:
| Table of Contents |
|---|
Steps to Export BDD Cases
Step 1: To export BDD cases, simply click on the Cases option in the top bar menu.
...
Step 2: Click on the vertical ellipsis icon (⋮) and select the Export to Feature File option from the dropdown menu.
...
| Info |
|---|
Post fetching, requirement information, and the feature files will be downloaded in a zip format. Users need to unzip the downloaded file. |
...
Feature File/Scenario Details
The exported feature files have the below information based on the choice of organization:
...
AIO Test Case field | Translated to in feature file |
|---|---|
Case key | Scenario tag eg. @AT-TC-121 |
Case title | Scenario/Scenario Outline name |
Case description | Scenario description |
Tags | Tags on each scenario |
Requirement | @JREQ-<storykey> eg. @JREQ-AT-1 |
Steps | Scenario Steps |
Examples | Examples |
Data | If pipe separated, then exported as datatable, else as docstring (encapsulated in ““) |
Exported File Example
The below file is exported when Organise by Requirements is selected.
Requirement key @JREQ-SCRUM-75 is the Jira requirement key as a feature-level tag.
The feature name is Requirement Summary, coming from the Jira Issue
Case keys are @TCMSTES-TC-327 and @TCMSTES-TC-329 added to each scenario
Tags of each case become scenario-level tags
Steps get added with corresponding keywords
...
For further queries and suggestions, please feel free to chat with reach out to our customer support servicevia help@aiotests.com.