It is recommended to run tests on the draft pipeline before publishing to ensure the pipeline is working as expected. Simulated tests allow you to test the pipeline without querying external systems unlike live tests. This saves you external api calls, however does not verify updates to end systems. This option is recommended when testing the logic of transformations within the pipeline. Simulated tests cannot be cancelled once started. There are no transactions logged for simulated tests.
To run a Simulated Test, go to the More Actions dropdown from the top-right corner and select Run Simulated Test option.
Creating a New Test
After clicking the Run Simulated Test option, in the box on the right-side click +New Test.
Now provide a Display Name and Description on what the test is verifying.
Lets use an example of camel casing the incoming Company Name from Hubspot and verify the results. Provide the mock input values, in this case, we are setting the incoming Hubspot company name as "hubspot inc". Click Add and then mention the value.
Now provide the expected outcome value. We expect the result to be "Hubspot Inc"
Save and Run
After adding the input values, click Save.
Now select the Test and click Run. The saved test can be rerun again in future using the Rerun option from the kebab menu.
Now, click Run again in the pop-up box.
Analyzing Results
Once you run the test, the results will be available in the right and bottom panel as shown below. Voila! We saw how simple it is to verify the transformation logic in the pipeline without running the full syncc cycle and calling external systems. A notification will also be sent to your in-app inbox upon completion of the test.
Exclusions
There are certain nodes that are excluded during the simulation test execution. Below is the full list. To verify these nodes, please use live tests.
- All action nodes are skipped during simulation test run.
- AttachRecord function
- Dedupe/Merge
- All Enrich functions