Tosca ExecutionLists, Results, and Distributed Execution
Introduction
Building tests is only half the job. ExecutionLists let you plan and run them in a controlled way and keep the results. This final Tosca lesson covers ExecutionLists, how they differ from the ScratchBook, and how Distributed Execution can speed up large runs.
Prerequisites
- TestCases that run successfully in the ScratchBook
- Basic familiarity with test reporting
Step-by-Step Guide
Step 1: Create an ExecutionList
An ExecutionList is a collection of TestCases that you want to execute in a specified order. Create lists around purposes, such as Smoke, Regression, or a specific release.
Step 2: Add TestCases as ExecutionEntries
Once a TestCase is added to a list it becomes an ExecutionEntry. You can reorder entries, skip them, or repeat them. Arrange them so that tests which set up data run before those that depend on it.
Step 3: Run the list
Run the whole list or selected entries. Unlike the ScratchBook, which is only for trial runs and does not keep results, an ExecutionList records results so you can report on them.
Step 4: Review results and logs
Inspect failed entries and their logs to decide whether the cause is a real defect, a test problem, or an environment issue. If you have already verified a test manually, the documentation notes you can set results manually, but use this sparingly to keep reporting trustworthy.
Step 5: Scale with Distributed Execution
Tosca Distributed Execution (DEX) runs tests across multiple agents so large suites finish faster. Setup involves a server component and execution agents, and the Tricentis documentation covers configuration. Check its best practices before creating new Modules if you plan to run on DEX agents.
FAQs
- What is the difference between the ScratchBook and an ExecutionList?
- The ScratchBook is for quick trial runs while building, and its results are not kept. An ExecutionList is for planned execution and records results.
- When should I use Distributed Execution?
- When your suite is large enough that sequential execution takes too long. It lets you spread tests across several machines.
Summary
Plan runs with ExecutionLists, use ExecutionEntries to control order, rely on recorded results instead of the ScratchBook for reporting, and use Distributed Execution when you need to scale. Consult the Tricentis documentation for your version for setup details.
Comments
Log in or create a free account to join the discussion.