qTest Scenario now supports JBehave Syntax. The following keywords are supported:
The following enhancements have been added:
- The "Meta" keyword is now supported for .story. This provides meta information and meta filtering.
- The "Feature" keyword is no longer required for .story.
- qTest Scenario now supports the comment step for .story.
- qTest Scenario now supports the use of tabular parameters. These parameters follow the gherkin tabular structure.
- qTest Scenario now supports the use of Brackets.
Step Status and Execution Status
Issue_step and Execution Status are now separated based on the issue or feature. This improves performance when getting a step's status and makes step status independent with each Jira Issue.
For example: with the ScenarioColor, we are able to mark passed, failed, or skipped colors for test steps on an individual issue instead of this applying for all issues that might include that same step.
Support for Jira GDPR API
qTest Scenario now supports the Jira GDPR API Migration change.
qTest Scenario Support for Gitlab Acadian URL Format
qTest Scenario 3.1.0 now supports the use of Gitlab Acadian URL formatting. Previously, only the default Gitlab URL format was supported (https://<vcs.provider>.com/<owner>/<repo>). You can now use the following URL formats:
Custom Issue Types in qTest Scenario
qTest Scenario now supports the use of Custom Issue types as well as Jira issue types. In the "Configure Projects" page, you now have two options for issue types:
- Jira system issue types (Story, Bug, Task, Sub-task, Epic)
- Custom issue types
Note: if you do not have any custom issue types in your Jira project, the configuration dialog will only show the one Jira system issue types panel.
Support for Jira Server URL With Context
You can now configure your qTest Scenario plugin using a Jira URL both with and without the context path.
- Without context path: http(s)://yourdomain.com/
- With context path: http://mydomain.com/jira
Bug Fixes and Improvements
|30057||BitBucket Cloud API||There are no longer issues with loading your Scenario content.|
|29249||Configuration||The "Return Results" process no longer fails due to an internal server error.|
|23209||Feature file||There is no longer a 50 character limit on the Feature File path.|
|26289||Gitlab URL||qTest Scenario 3.1.0 now supports the use of Gitlab Acadian URL formatting. Previously, only the default Gitlab URL format was supported (see "New Features and Enhancements" section).|
|25660||Issue Types||You can now use custom issue types within your Scenario project configuration (see "New Features and Enhancements" section).|
|NA||Pagination||There are no longer pagination issues when using Bitbucket Cloud.|
|16819, 21723||Plugin configuration||There is no longer any issue configuring your Scenario plugin while also using a context path for Jira server.|