Overview

Testing your graph before deploying to Production helps you confirm that records route the way you expect, without surprises in your live org. LeanData gives you several ways to validate a graph, from simulating a single record inside the Graph Editor to running large batches of existing records through your logic.

Before you begin, consider your testing environment. Testing with a full dataset gives you the most realistic results, so a Full Sandbox is recommended. If a Full Sandbox is not available, you can test in any recently refreshed Sandbox. Whichever environment you use, aim to trigger every node in your graph at least once.

 

Testing Options

LeanData supports three main approaches to testing a graph. You can use them on their own or together, depending on how thoroughly you want to validate your logic.

Option 1: Routing Preview

Routing Preview lets you simulate sending a single test record through your graph logic directly from the Graph Editor. It previews the path and outcome of a record's journey without creating test records or modifying existing records in Salesforce, so it is the fastest way to spot-check a scenario or troubleshoot a specific path.

Use Routing Preview when you want to:

• Confirm how a specific record would route before committing any changes in Salesforce.
• Test how different field values change a record's path by simulating values on the test record.
• Troubleshoot a single record's outcome without setting up a full batch test.

To get started, open your graph in FlowBuilder, select a Trigger node and entry point, choose a test record, and click Run Test. Results display in an Audit Log format so you can trace each step of the record's journey. For full setup steps, field configuration, and guidance on interpreting results, see the Routing Preview Guide.

Option 2: Routing Scheduler

The Routing Scheduler lets you run a large batch of existing records through your graph, which is useful for confirming behavior at scale. Because you are using records that already exist, you do not need to build a test case for every requirement or edge scenario by hand. Pair this with Routing Insights to quickly see which nodes have and have not been triggered. Because these records are committed in Salesforce, this approach also surfaces validation rules, errors, and other automations that run at the same time and can affect the final outcome.

Best practices for testing with the Routing Scheduler:

• Pull a report of the leads you plan to route, with a diverse selection of records.
• Include leads that meet your entry criteria along with leads that do not, so you can validate the criteria.
• Cover different conditions throughout your graph by including leads that satisfy different criteria.
• Filter out converted leads by setting your report filter to Converted = false.
• Send leads in batches of no more than 20 to 50 to keep auditing manageable.

Option 3: Manual Record Creation

You can also create records by hand that meet the various conditions built into your graph. This takes more effort, but it gives you precise control over each scenario and ensures every condition triggers as expected. Because you are working with real records in Salesforce, it also reveals how validation rules, errors, and other automations interact with your routing and shape the final outcome, which a preview on its own would not catch.

Best practices for manual testing:

• Create a diverse set of test records that cover multiple scenarios.
• Include records that meet and do not meet entry criteria to validate routing behavior.
• Test every condition in your graph by including records that satisfy different criteria.
• Record your tests and results systematically so you can audit them later.

 

Additional Testing Tools

• Audit Logs track the routing path of your test records so you can confirm the logic is working correctly. For more detail, see the Routing - Audit Logs Guide, and review the Audit Logs Error Messages document for explanations of common errors.
• Routing Insights analyzes high-level routing results so you can optimize your graph. For more detail, see the Routing Insights & Deployment History Guide.

 

Summary

Testing before deployment protects your Production org from routing surprises. Use Routing Preview for fast, targeted checks of individual records inside the Graph Editor, the Routing Scheduler for batch validation against real data, and manual record creation when you need full control over specific scenarios. Audit Logs and Routing Insights help you confirm and refine the results along the way.

For questions or additional assistance, please contact LeanData Support.