What can you do using the Flow Tester?

When you use the Flow Tester to test a flow, all the activities in the flow are executed. While the flow tester is active, you cannot add or delete an Activity in the flow.

When an Activity is being executed, a blue animation is displayed around it. When the execution of the Activity is completed, the Activity is highlighted in the flow and the blue animation moves to the next Activity. Activities that have not completed execution are greyed out. This helps you see the progress made in the execution of the flow.

Attention: It is a good practice to stop testing by clicking Stop Testing when you finish running a flow in the Flow Tester, as the login session remains active for the entire time that you are in the testing mode.

Handling errors

If the Activity encounters an error, it is highlighted with a red colored border and a red error icon is displayed on the the Error handler tab (if the error handler is run in the background). You can click the Error handler tab to find out till where the execution took place successfully. Note that when you navigate back to the Main flow, the red error icon is not displayed on the Error handler tab.

Note:

If you start the execution from the Error handler tab, execution is moved on to the Main flow tab (as an error handler is always a part of the main flow).
You can, however, start a test from a tile on the Error Handler tab. In this case, the execution starts from the Error Handler tab.
If the execution is started from a sub-flow, the execution does not move to the Main flow and acts as a normal tile execution (as a sub-flow is an independent flow).

Executing the flow from a specific Activity onwards

You can debug a specific Activity in the Main flow or Error Handler flow. If it is successful, the output is shown on the Output tab. If an Activity does not have any output (for example, the Return Activity), it shows the Output tab as blank. If the Activity is erroneous, the error is shown on the Errors tab.

To execute the flow from a specific Activity (and not from the beginning of the flow) with different input data, perform the following steps.

Note:

This can be done only after the entire flow has been executed at least once.
When you start the execution of a flow from a specific Activity in the flow, you cannot start the execution again from any Activity before the current Activity. If you need to do that, you must launch a new test.
For example, a flow includes A1 -> A2 -> A3 -> A4 -> A5 activities and execution is started from the A3 Activity onwards. In subsequent executions, you cannot start the execution from any Activity before A3; execution always starts from A3 onwards. If you want to run the flow from an Activity before A3, you must launch a new test.

Procedure

Select the Activity from which you want to run the flow.
The Activity is highlighted in blue. The Activity data is displayed on the Inputs and Outputs tab. If an error is returned, an Error tab is displayed in place of the Outputs tab.
On the Inputs tab, change the input values as required. You cannot do dynamic mappings here.
Click Run test from this Activity.

The execution begins from the current Activity. The logs are also displayed only for the current Activity and subsequent activities in the flow.

Note: Once the execution starts from a tile, you cannot access preceding tasks executed in the previous runs. The previous activities are greyed out. If you want to run the flow from a previous Activity, you must launch a new test.

Logging information

As the activities are executed, the runtime engine logs for the activities are displayed in the Logs output window. The format of the logs is similar to the logs displayed while running an app executable.

To copy these logs, you can click Copy logs.

You can also switch from the Flow logs view to the Activity data view by clicking Activity data.