Scenario 2.2.2 Release Notes
February 28, 2019
Enhancements
We are pleased to announce the Release of Scenario 2.2.2 to our OnPremise customers. This Release includes several enhancements such as working with multiple repos, branch management, as well as compatibility with Jira Service desk and JBehave.
Note, that with this new version, there have been changes to Scenario configuration, as well as the BDD workflow. Read these articles for additional information:
Enhanced Environment for Working with Repos
Users can now link multiple Git Repositories to a single Jira Project. This is very useful for teams using "components," or, teams that are using multiple kinds of applications within the same Jira project.
Use Case
I have an application with a web, Android, and iOS front end, and these are all managed in the same Jira project. Each front end is linked to its own separate BDD Git Repository from Bitbucket. Now, I can link to all three of these Repositories within my one Jira Project.
GitLab Support
qTest Scenario now supports all versions of Gitlab, which includes:
-
GitLab Cloud
-
GitLab Enterprise Edition
-
GitLab Community Edition
GitLab support has the same functionality that both GitHub and Bitbucket currently have in Scenario. So, Jira Admins are able to:
-
Add a GitLab repo
-
Set up and select a default branch from their GitLab instance
Non-admin users in Jira are able to:
-
Create features for Jira tickets
-
Link and unlink feature files
-
Switch branches
-
Switch repos
-
Search feature file
This is an optional ability and depends on the GitLab api/sdk.
Branch Management
Users can now better manage branches. When configuring your Git Repository, you can now set up a default branch. You can also set up a branch on the issue.
Compatibility with Jira Service Desk and JBehave
Jira Service Desk
qTest Scenario is now compatible with Jira Service Desk and is compatible with the latest versions of Jira (v7.12) and Jira Service Desk (v3.15x).
JBehave
qTest Scenario 2.1.0 is now compatible with both .feature and .story as file extensions. This is the first step towards full compatibility with JBehave.
Enhanced Search Capabilities
Users can also search for feature files faster by searching from within the Scenario UI. Previously, users had to search from within the git Provider API.
Changing the qTest Site from within Scenario
You can now change the linked qTest site from within Scenario. This is helpful for Administrators who may work within multiple qTest sites, and also helps Admins better activate Enterprise Features.
Auto-scanning Source Code
Developers can now auto-scan Scenario source code in order to detect Open Source issues.
Bug Fixes and Improvements
Ticket # | Component | Description |
---|---|---|
17967 | Navigation | The BDD Scenario section is no longer at the bottom of the issue below the comments, and is, instead, below the description section. |
19583, 19186 | Search | There is now greater pagination when searching for branches and feature files. |
NA | Feature files |
Feature file names and paths are no longer forcibly changed to lowercase letters. This was affecting users' integrations with Bitbucket. |
NA | Visual |
The Scenario version number now displays at the bottom of the page. |
NA | Actions |
Users can now create, edit, and delete actions from within the Enterprise Settings tab. |
NA | Repositories |
You can create a new repository when using a new Jira account. |
NA | Jira Access |
Users within a private Jira instance with Read-only access can now view Scenarios. Previously, these users needed Editor access in order to view Scenario. from within a private Jira instance. |
NA | Feature Files |
Feature file searching has been improved. Users can now search for a feature file from within a subfolder and link that feature file to a ticket. Previously, users could only search for feature files from outside of the subfolder and were unable to select or link to tickets. |