Any clarity on how this is not an implicit requirement?
All of our test cases can pretty much stand alone, so running in any order is fine. When tests have to run in a certain flow we put them into folders, but in terms of priority during the beginning of cycle it would be great to have a few that are always ones we do first not based on priority alone. For us it is just plain to make the job of a tester more logical, it really helps to be able to have a defined order simply to make the way testers will mark work as done less random.
Grouping tests, can be done by folder, but when you can see all the tests in a feature in one place it gets easier to spot when a flow is missing a boundary case or a negative-case when you are able to bunch related tests manually. Even if it is ability to "sort" on a field that will help I guess. Thanks.
