Best practices | Execution | ExecutionLists
An ExecutionList is a collection of TestCases in a specific order that you define. It allows you to run multiple TestCases without having to trigger each TestCase separately. Plus, ExecutionLists keep all results, creating a record of your application's performance over time.
When it comes to ExecutionLists, keep these things in mind:
-
Group your TestCases by business workflow. This makes it easier to keep track of your objectives.
-
Give each ExecutionList a unique and descriptive name. This makes it easier to identify the right ExecutionList in search results and reports. We recommend this naming convention:
application name or abbreviation | workflow | sub-workflow
-
Add folders to your ExecutionList. This makes it easier to read, understand, and work with complex test flows.
We recommend that you drag and drop TestCase folders onto your ExecutionList. That way, the structure in the ExecutionList follows the structure in the TestCases section, which makes your TestCases quick and easy to find.
Good names and folders make ExecutionLists easy to find, work with, and analyze
What's next
If you haven't yet, check out our other best practices articles.