#SalesforceWinter27 [Tip 35] (Video 4:45) - Debug and Test Flows in One Place with Test Mode (Beta)

Winter '27 brings debugging and testing together in Flow Builder with a new Test Mode, now in beta.

Click Test at the top of Flow Builder and the canvas switches to a test view. Enter your inputs, such as the record that triggers the flow or values for variables, and run the scenario. If you'll need that scenario again, save it. Next time, it's one click instead of re-entering every input.

You can go one step further with Scenario Testing Automation. Add assertions, which are conditions that describe the result you expect, and a saved scenario reports pass or fail each time it runs. Saved scenarios with assertions also show coverage: which elements and paths ran successfully.

Test Mode works for autolaunched and record-triggered flows. Click Build to switch back.

Product Area: Flow

To turn it on, go to Setup, open Process Automation Settings, and select Flow Test Mode (Beta).

Here it is in action.

win27-flow-test-mode.mp4

How It is Useful

Salesforce's reasoning is that debugging and testing used to live in separate parts of Flow Builder. Test Mode brings them together, so you can confirm a flow works now and still works after you change it.

Most flows get tested once, when they're built, by someone clicking Debug with whatever record they had handy. Six months later another admin adds a branch, and nobody re-runs the original checks because nobody saved them. Saved scenarios with assertions turn those checks into something the next person can run in seconds. Regression testing becomes part of the screen you already debug in, instead of a separate step most admins skip.

References & Useful URLs



Found this useful? Hit like, and drop a comment — I read every one, and your feedback decides which tips make the list.