Flow tests versus Flow Debugger
Key Takeaway
The flow type picks the tool. Record-triggered and autolaunched flows use Test Mode, while all other flow types, such as screen flows, use the Flow Builder debugger.
Before you activate a flow, you test it to catch errors, check every path, and avoid unwanted data changes. Flow Builder gives you two tools for this. The Flow Builder debugger runs a flow step by step, so you can see where the flow goes and where it breaks. Test Mode (beta) lets you save reusable test scenarios and can check results automatically with assertions.
Which tool to use
The flow type decides which tool you use. Record-triggered and autolaunched flows use Test Mode instead of the debugger. All other flow types, such as screen flows, use the Flow Builder debugger.
Data Cloud-triggered flows use automated flow testing to verify expected results and find runtime failures before you activate them.
You build two flows. One is a screen flow that guides a sales rep through logging a customer call. The other is a record-triggered flow that runs when an Opportunity's Stage changes. You test the screen flow in the debugger. You test the record-triggered flow in Test Mode.