Flow Tester

After you design a flow, use the Flow Tester to test the flow.

When designing a flow, runtime errors can go undetected until you build the app to execute the flow. It can become particularly cumbersome to test flows that start with a trigger since the triggers activate based on an external event. So, before you can test the flow, you need to configure the external app to send a message to the trigger to activate the trigger and consequently execute the flow. The Flow Tester eliminates the need to activate the trigger to execute the flow.

You provide the input to the flow in the Flow Tester. The Flow Tester executes the flow on demand without using a trigger. Each Activity executes independently and displays its logs. This lets you detect errors in the flow upfront without actually building the app.

Note:

  • The Flow Tester takes some time to start as the engine is built from scratch every time you start the Flow Tester. The time taken to start the Flow Tester depends upon the number of contributions used in the app.

  • The Flow Tester is disabled when Activity type contributions are missing in the flow execution.

  • Expressions and functions are not evaluated in the Flow Tester. Input provided is passed as is.

  • You can run the Flow Tester in the debug mode with the following features only:
    • Test run the flow
    • See the flow execution
    • Select an Activity that is executed and see the inputs and outputs
    • Change the inputs to other valid values and start the Activity from that point onwards
  • You cannot:
    • Insert a debug point and stop the flow execution at a tile
    • Skip a tile from test execution