Make changes to test design automatically in test runs
A feature that many Testersuite customers have requested is to make changes to test cases in test design automatically in test runs. This release makes this possible. From now on, when you edit a test case that already appears in test runs, the following question will be asked when saving the test case:
When you confirm, the test case changes are also made to the test case in test runs.
Note: Making changes from test design is possible only for test cases that have the output status Not Started .
Test case in test run is not assigned until status change
When you start running a test case in a test run, which is assigned to a group or which does not have a tester, that automatically makes you the tester of that test case. Previously, you were automatically entered as a tester as soon as you clicked the Run Steps button. As of this release, the test case is only assigned to you when you actually execute the test steps. For example, when you click OK or Not OK on a test step, or click OK on an entire test case at once.
Output status test cases in products & requirements overview
We always try to make the testing process as transparent and traceable as possible. In that context, the column Output status test cases has become available in the list of products. With this new column you can immediately see the progress of testing per product. The column shows the number of test cases in test runs related to that product. This gives you information about the test progress of your products at a glance.
You simply add the column yourself to the overview. From the column it is possible to click through to the corresponding test runs in which the test cases for that particular product are located.
When you export the list of products, the new column 'Progress of test cases' is converted to five columns containing the numbers (one column for each status). This allows further analysis of the data in Excel.
Output status test cases in requirements list
The output status test case column has also become available in the requirements list. This works in the same way as described above for the product list. This way you also have information about the test progress of your requirements at a glance in the requirements list....
Output status test scenarios in test scenario overview
Also in the table with test scenarios the column Output status has been added. This gives you direct insight into how often a test scenario occurs in test runs and what its execution status is. You can also click through from the column to the relevant test runs. You activate the column yourself on the overview page of your test scenarios.
Azure DevOps handler and area path viewable in defect
We have extended our Azure DevOps integration to make the link between the two systems more viewable. If a defect has a linked Azure DevOps work item, the Azure Handler and Area Path fields are now viewable with the defect's detail data. Of course, this information remains synchronized with the information from the Azure DevOps work item.
Sharing reports within one specific Test cycle
When creating a custom report it was already possible to share the report with other users. Now the option is added to only share the report within the current Test cycle . This way all participants of that Test cycle can use that specific report. The option can be found in the 'Share report' field when creating or editing a custom report.
Hyperlink to defect in defects export
Exporting your defects is hugely useful for sharing them with stakeholders outside Testersuite. To get back to Testersuite from the export list, the column 'Defect URL' has now been added at the back of the export file. This allows you to go to the relevant defect in Testersuite to view, for example, the attachments, or additional information.