​

Test your Blueprint

Before deploying your Blueprint, you can run it directly in Leapter to verify that it behaves as expected. Testing lets you provide sample inputs, execute the logic, and inspect the outputs — all without leaving the editor.

​

Run your Blueprint

​

Step 1: Open the Run panel

Switch to the Run tab in the left panel, or click the green play button on the Start node to open the Run Logic panel.

​

Step 2: Provide input values

The Run Logic panel displays an input field for each parameter defined in your Blueprint’s Data Contract. The panel reflects the configuration of your inputs:

• Field type matches the data type you defined (string, number, boolean, date, or enum)
• Required inputs are marked with an asterisk (*) and must be filled before you can run
• Optional inputs can be left empty — your Blueprint will handle the absence based on its logic
• Info icon next to each field shows the input description, helping you understand what value to provide

Fill in the values you want to test with, then click Run Logic.

​

Step 3: Review the results

Once the Blueprint finishes executing, the panel updates to show the results: The results panel displays:

• Status — whether the run completed successfully or encountered an error
• Output tab — each output parameter and its resulting value
• Replay tab — the number of steps executed (e.g., “Replay 33”)
• Run Again — a button to quickly re-run with new inputs

On the canvas, the execution path is highlighted with green dashed lines, showing which branches and elements were visited during the run. Each visited element shows a step number in a green circle (e.g., 6, 7, 8), so you can see the exact order of execution. This helps you visually confirm that your Blueprint followed the expected path through its logic.

​

Replay: step through the execution

After a run, you can step through every event that occurred during execution. This is especially useful for debugging unexpected results or understanding how your Blueprint processes specific inputs. Click the Replay tab (or the “View Replay” button) to open the replay timeline.

​

The step timeline

The left panel shows all visited steps in order:

• Each step has a number and a name (e.g., “1 start”, “6 Cart validation check”, “18 Weekend rate assessment”)
• The currently selected step is highlighted
• Call nodes show their sub-steps (e.g., “2-5”) and a Step In button to view the called Blueprint’s internal execution

Click any step to jump to it. The canvas scrolls to show the corresponding element.

​

Step data

Below the timeline, the Step Data section shows the state of all variables at the selected step:

• Input Data — the input values provided to the Blueprint
• Local Data — the current values of all local variables at that point in execution
• Output Data — the output values (shown at steps where outputs are set)

​

The values popup

When you select a step, a Values popup appears on the canvas next to the active element. It shows a compact view of Input, Output, and Local data at that moment — so you can see variable values without looking away from the diagram.

​

Replay controls

The replay controls appear both in the left panel and at the top of the canvas: During replay, the editor is in Read Only mode — you cannot edit the Blueprint until you stop the replay.

​

What to do next

• Test Suites — create and auto-generate test suites for systematic testing
• Inputs and Outputs — configure the data your Blueprint works with