Ability to 'Search and Map' to improve usability while mapping test cases and Requirement
Currently, when the User Maps the Requirement to Testcase and Testcase to requirement there is no search and map of the entity. So the user has to go to each and every folder and then map the Testcase or requirement on the pop-up to map test cases or map requirements, give the user the ability to either browse through the directory structure or search. External ID:-ZENT-I-125Need ability to Edit/Map/Delete tests found via Search
When Tests are found via Search, only the function Export is available at the moment. Once at least one of the found tests is selected, other functions should be available as well: Edit, Map, Delete, Clone (single test or in bulk). External ID:- ZENT-I-362Support for parametrization
Need the ability to reuse test case templates through parametrization in order to allow scaling effectively. I.e., having one test case, and then feeding in parameter values to create variations of the test case at run time so that the same test case can be executed repeatedly with different data values. External ID :- ZENT-I-6Retain folder structure on refresh in Zephyr Enterprise
When we navigate and select a particular test case within a folder there are 2 issues that we are seeing: 1. Folder structure is not retained when the same URL is refreshed or opened in another tab of the browser. 2. After clicking on the test case, the URL where the test case details and test case description are shown, can not be retained on click of a refresh or opening in the other tab in the browser. It is taking to test case list page. OLD ID:-ZENT-I-423
Create a test phase directly from repository folder
As a tester, I get a story (requirement\new feature) to test, then: 1. I begin to design the test cases I going to run and build the test tree under the repository. 2. Map the testing to the requirement. 3. Open a test phase under the test cycle for this story. 4. Move to test execution to run the test phase. I want the option to create test phase directly from the repository folder. Furthermore, I usually, during the test execution, think of more scenarios to test, and I need to go the whole process again from 1-4 for the new scenarios. I want the option to run the test case as part of the phase, from the test case in the repository level.Improve the feature of un-mapping a Test from a requirement
Currently, there is no simple way to remove the existing mapping between a Test and a Requirement. This can only be done individually for each test through several non-intuitive steps. We need a more efficiently designed functionality, which allows us to un-map a Test from a Requirement and vice versa individually and in bulk. OLD ID:-ZENT-I-366Improve usability for creating test cases in one go
Currently, creating a new test case requires two steps: Create the test case - which simply creates an untitled test case then update the test case - which opens a new test case and lets the user update the details As a user creating multiple test cases, I'd like to be able to create it in one go, similar to the Jira issue creation pop-up. Also, this should enforce that all mandatory fields are properly filled out before creating test cases. OLD ID :-ZENT-I-126Get Traceable Path from Root - Search for test case in Repo, and locate which folder it is in
Need to be able to search for a particular test case by name or by ID in the Test Repository within the "Folder" view. Currently, it only shows the folder names while using the filter. We need to be able to tell in a Release folder with let's say 100 subfolders where a particular test case resides (which exact subfolder), either by test case ID or by the test case name. Not sure if this will require some sort of additional search functionality other than the filter or "Search view" OLD ID:- ZENT-I-438Support workflows for Test Cycles, Test Phases, and Test Cases
Use case 1 As a User, I need native support for Test Case workflow in order to understand which test cases are ready for review, which are ready for automation, which is approved, etc Use case 2 Allow the User to view issues only when the task reaches "Approved" status. They would also like to restrict editing in the Test Steps before the Test Execution status has changed to "Approved" OLD ID:- ZENT-I-19