Hello! It would be great if Test Plans allowed users to customize the order of tests themselves. Not just the order in which they appear in folders, but the ability to manually move them to the desired position. In addition, it would be nice to be able to add the same test several times, since sometimes there may be several places where the same test is needed, and making a bunch of duplicates is not very convenient. Maybe I’m missing something and these features already exist?
For example, if I’ve already created a plan or am in the process of creating one, and I realize that a test case (say, TC-148) should come before TC-147, it would be much easier to reorder them directly here, without having to go to the Test Cases section to change their positions.
Also, if there are, say, 500 or 1,000 test cases, it would be difficult to maintain a single specific order that’s convenient to use across all Test Plans and similar areas.
Hi and welcome to the Testiny forum!
I think you’re using the test plan in a different way than it is designed for.
Test plans in Testiny can dynamically create sets of test cases using multiple queries (filters, folders, and specific test cases) and then create test runs from these sets.
It’s neither intended to change the order test cases are executed, nor would it show test cases twice (if a test cases is returned by 2 queries, it will still only show up once in the test plan).
That is because to execute tests you would create a test run out of a test plan and the same principles apply for test runs.
If you want to change the order of test cases, you can do that in the Test Cases view by moving test cases up and down within a folder.
I understand the need to execute a test case twice e.g. on different environments. Unfortunately, right now you have to create 2 separate test runs for this scenario.
We do have a feature on our roadmap to allow a more data driven approach which could be used for this scenario.
Best regards,
Alex
Thanks for the clarification! I leave this topic open for others to vote on this feature request.
If somebody reads this request and would also like to have this feature, make sure to vote for this topic. We do consider the number of votes for feature requests in our roadmap and priority planning.
Best regards,
Alex