- As a user, I need an easy and accessible way to navigate the screen while creating or editing a test case. Currently, you cannot use tab to move to the next text box when creating or updating a test case. It is also very difficult to click to the next test step without it creating a second step below the step you're working on.
- Hi Team, Folder copy from test repository is not retaining the testcase order, Instead reordering based on testcase id. for example in a folder ACB we have 3 testcases with names one(Order 1), Two(Order2) and Three(Order 3). Then I copied the “abc” folder to "def” folder, now the order is changing based on testcase id.
- When creating and executing test cases, having the ability to reference a test case within another test case step/detail will save time, effort, and confusion for users. Being able to just reference an existing test case, instead of re-writing it, will increase efficiency as the user creating the test case and the user who are executing the test case (this allows users to either navigate to the reference test case to follow, or skip it because they already have that knowledge/know the steps.
- Creating folder hierarchies and organizing test sets/cases/requirements etc is a large part of keeping our repos clean and legible. Without the ability to reorder these folders and entities we are forced to use alphabetical prefix that make reading folders more difficult at a glance, or be stuck with disorganized cases (or manually adding them to sets one by one in the right order for potentially thousands of cases) because a new test case was added that is showing in last place when it should come after the 50th case for example. Added an example below with names for visibility, Test Case 1 and 2 were initially created, and then a new feature or change order came in that added a new case (1.5). In our ordering, 1.5 comes before 2 can be run but because it was created later it's automatically sent to the bottom (sorted by ID). Again our option becomes to prefix them with an ordering of IDs and sort by name which is much more tedious and harder to manage. It becomes especially rough when it comes in 50-100-200+ test cases later, or finding it afterwards to create execution sets.
- To make it more secure that one or more test cases will be deleted erroneously it would be good to have the possibility to configure an four eye principe for deleting test cases. If user A decide to delete a test case user B get a notification that user A want to delete one or more TC's. Only when both users confirm the deletion will be executed.
- When editing a test case, I don't always want a new version created. It would be nice to have a way to un-do or re-do changes before committing a new version to the repository. (it would be helpful to be able to un-do an action such as making changes to or deleting a test step)
- it would be helpful to be able to drag and drop more than just one test step at a time, especially for long test cases
- As a user, I would like to be able to create a test case directly from a requirement. - Open requirement - Create a test case - Test case would then be mapped from the requirement it was created from
Import new Test Steps section (Test Steps, Test Data, and Expected Results) to an existing Test CaseThe user should be able to create an Import map and file to load new Test Steps (at least Test Steps, Test Data, and Excepted results) to a pre-existing Test Case in the Test Repository. Maybe by using the Test Case Id as a unique identifier for the Import processing.