Add execution steps

Specify which activities to execute by adding steps.

Click Add execute step.

The Add execute step pop-up appears.
On the Node list, select an activity and click Save.

If you select an activity that is not in the execution path, the test fails.

The execute step is added for the activity and the job will evaluate to that point and the activity selected in the Execute step will be completed. Once the execute step is added for an activity, such as Activity1, the entry is listed as Execute: Activity1 with a Green color tick mark under Steps/Assertions on the Execution path tab. Once a step is added, a Play button is automatically added before the step. The Play button for the entries appears only when you restart the test. When editing a test, you can use the Play button to perform the test to a certain point.

Editing a step will execute to that point. Whenever you edit the test case, you must restart the test case.
Similarly, add the steps to execute for the other nodes including the end node in the map.
On the modeling bar, click Restart test.

The Play button  becomes available for the execution steps.
To execute your test to a point, click .
The job runs to that point for execution. For example, if there are 10 execute steps/assertions, and you press play at the sixth execute step, the job runs from the first step to the sixth step for execution.
- The specified initialization data is used to create the job.
- The script is executed using any configuration for the nodes. If only one configuration exists, use it each time the node becomes pending.
- If more than one configuration exists, each time the node becomes pending the next configuration is used. If there are not enough configurations, the test fails.
- When there is no activity to execute, or no assertion to check, the test fails, and an error appears.