CSV-Import: Owner is mapped to Jira-userkey
During importing testcases we came across a big problem: When importing testcases from a csv-File to Zephyr the owner is mapped to the userkey in Jira. This is an unique ID which cannot be changed, but the displayed username can be different for example after changing the name (marriage etc.). So you sometimes cannot import the owner by the username even if it is displayed in the users profile. If you export a testcase the field owner also contains the Jira-userkey. This behaviour is misleading, so the field owner should be mapped to the username not the userkey. Is there any possibility to avoid this situation?
Ability to display only test cases contained in selected folder
When a folder is selected in the test library, all tests contained within the folder are listed, including those in subfolders of the selected folder. This makes it difficult to determine which tests belong only to the selected folder. For example, consider a top-level folder named General Tests that contains five tests and a subfolder named Advanced Tests that contains fifty tests. If only the five tests belonging to General Tests need to be edited, the user has to select General Teststhen manually find the five tests out of the fifty-five listed that belong only to theGeneral Tests folder. Compare this behavior to how File Explorer behaves in Windows. When a folder is opened, all files within the folder and its subfolders are not displayed. Instead, only files within the selected folder are displayed, while all files within the subfolders remain hidden. This feature should be implemented as a toggle in the test library so the user can choose whether to display all tests within the selected folder and its subfolders or just the tests in the selected folder.Ability to open a test's folder from the test details
The Folder field in the Details tab of a test shows the location of the test using a folder path. However, this path cannot be selected. If a user is viewing a test and wants to open its folder, they will have to open the test library and manually expand all folders in the path. A link to the test's folder should be present in the test details so users can quickly navigate to the location of the test and other related tests.
Custom Status should not default to Done
When using the status "Blocked", a test case execution is considered "Done". We most often use "Blocked" as a temporary status to note when something's start or work is impeded, however, it instead gives the team credit for complete work. We introduced a custom status instead, but all custom statuses are also considered "Done". Zephyr Scale should allow us to indicate whether a custom status is "Done" or not.
Test Case Search Criteria - Search within Test Script
The current Zephyr Scale Test Case search function only allows search via criteria which is available on the Test CaseDetailstab. Please allow users to additional Search Criteria to search with the Test Script tab. For example: search on Expected Result contains 'blah'Ability to click on the summary shown in graphs, lists, reports to then display the source data
Many Test Managers set up Dashboards using the SmartBear reports, graphs, lists etc as a one-stop high-level view for reporting and monitoring. However we are not able to drill down into the report, graph, lists etc to see the specific group of artefacts which make up the report result; unlike Jira allows with it's own graphs. Example: The Zephyr ScaleTest execution results (progress) 'report' chart returns a pie-chart which displays test execution results grouped by execution status. It would be great if we could click on a status in chart (e.g. Blocked) to then be taken to a view which lists all of the applicable tests for that status.
Need to be able to bulk move test cases into folders
Folder is a field in a test case and can be a good way to organize test cases, but for some reason you are not able to bulk edit the folder field. Managing test cases through the usage of folders then becomes a pure manual process as each test case has to be edited one at a time which would be a lengthy endeavor for something that seemingly should be handled by the bulk update function.Peer review for test cases
Comments for the test case is not a workaround for does not work when you have many test steps. Add ability to peer review individual steps of test case. This includes ability to dismiss, respond, and tracking reviews. A requirement can be that this is possible only if the test case is in Draft state.Ability to change version number of test case
Currently version number for test cases increment by 1 starting at 1.0. The problem is that smaller changes are not able to be tracked other than through History page. Couple of options could be: 1. Ability to append text to version number of test case 2. Ability to track smaller changes - e.g. 1.1, 1.2, etc.Capability to restrict or revert test changes
Zephyr Scale Currently, all users of have the ability to modify test cases. This is a problem when new users unknowingly modifies a test case. History does keep track of changes, but requires manual effort to revert changes. Adding an ability to either restrict changes, or revert changes would be helpful.
Zephyr Scale Feature Requests
15 Posts
