Within a test campaign, all tests are treated as independent entities. There is no way to enforce a specific execution order or to define that one test is a prerequisite for another. Testers must rely on specific order or naming conventions to follow the correct sequence, which is error-prone.

A user should be able to define dependencies between tests within the same campaign. hen setting up a test campaign, there should be a mechanism to mark a test (e.g., Test B) as dependent on another test (e.g., Test A) :

• Test B should be blocked or not executable as long as its prerequisite, Test A, has not been successfully completed (i.e., passed).
• The UI should clearly indicate that Test B is blocked and show which test(s) it is waiting for.