With this release, the following changes, additions and enhancements have been made to Testersuite :
New look for detail and edit screens
In order to make Testersuite clearer, and as a step towards a new version of the Testersuite front-end, the detail and edit screens have been given a new look. Everything here has been given a bit more space to make the screens clearer and clearer. Any integration details have been given a separate place on the screen from the other details, so you can always find them in the same place:
Added option to only be able to log in with SSO
A common desire is to only be able to log in via SSO. This is now possible with a new setting in the SSO settings in the administrator portal:
If this setting is on, it is no longer possible for users to log in with a Testersuite username and password, but only with the SSO link set. The login screen looks different in this case. Only a Testersuite administrator can still log in with the Testersuite username and password in this case:
Azure DevOps link: automatically relate bugs from Testersuite to the right work item
Through the Azure DevOps link, it is possible to bring User Stories or Product Backlog Items from Azure DevOps into Testersuite as requirements. When you test these in Testersuite , defects may arise. These defects can then be shot back to Azure DevOps as a Bug so they can be picked up by those responsible.
As of this release, the Bug created based on the Testersuite defect in Azure Devops is automatically related to the original User Story/Product Backlog item. This happens automatically if the defect in Testersuite is linked to the requirement based on this User Story/Product Backlog Item.
Tester can change the tester in a test run when this concerns a group he is part of
It was already possible for a tester to assign a test case in a test run to another tester if desired. As of this release, this is also possible for groups to which the tester belongs.
