Testing your flow is a crucial step before rolling it out to your Production org. But what is the ideal environment, and what are your options?
It’s best to test with a full dataset (enabling you to use Option 1 below), so testing in a Full Sandbox is recommended. However, if that’s not available, you can test within any recently refreshed Sandbox. Ideally, ensure that every node in your flow is triggered at least once during testing.
Option 1: Using Routing Scheduler
The Routing Scheduler allows you to confirm that everything functions as expected when processing a large number of leads. This method is quicker because it enables you to run a large batch of existing leads through your flow without manually creating test cases for every unique requirement or edge scenario. Additionally, Routing Insights helps you quickly determine which nodes have or haven’t been triggered.
Best Practices for Testing with One-Time Router:
-
Pull a report of leads you plan to send through One-Time Routing, ensuring a diverse selection.
-
Include leads that meet entry criteria as well as those that do not, to validate your criteria.
-
Test various conditions throughout your flow by including leads that meet different criteria.
-
Filter out converted leads by setting your report filter to
Converted = false. -
Send in batches of no more than 20–50 leads to simplify auditing.
Option 2: Manual Lead Creation for Targeted Testing
Another approach is manually creating leads that meet the various conditions built into your flow. This ensures each condition triggers as expected.
Best Practices for Manual Testing:
-
Create a diverse set of test leads to cover multiple scenarios.
-
Include leads that meet and do not meet entry criteria to validate routing behavior.
-
Test all flow conditions by incorporating leads that fulfill different criteria.
- Record your tests and the results in this template in order to audit the results.
-
Record your tests and results in a standardized template for auditing.
Additional Testing Tools & Insights
✓ Use Audit Logs to track the routing path of test leads and confirm that the logic is functioning correctly. For more information on our Audit Logs, be sure to review the Routing - Audit Logs Guide. Also, common errors found in Audit Logs are explained in the Audit Logs Error Messages document.
✓ Leverage Routing Insights to analyze high-level routing results and optimize your flow accordingly. Refer to our Routing Insights & Deployment History Guide.
By following these best practices, you can ensure your flow is tested thoroughly and performs as expected before deploying to Production.