You can debug a Tool in test mode to ensure the Tool processes your records as expected before using the Tool. When you run a Tool in test mode, you can review the processing behaviour of each step (transformation, mapping, filter, or hook) and fine-tune your configurations to handle all variations of results or responses from each step.
Before performing test runs, you must:
-
Configure your Tool input.
-
Configure your lookups and imports.
-
Provide mock Tool input data for your Tool input and any lookup step you want to test.
-
Provide mock response data for each import.
Similar to the test mode in the Flow builder, you can view test run results for each step and the execution logs for the hooks.
Run test is disabled if any of the following are true:
-
If the tool input is not configured.
-
If mock data is not available in the Tool input
You can run a test : by clicking Run test at the top right of the Tool builder.
You can watch a Tool as it's running and access the errors as they are reported (even before the Tool run has been completed) using the Run console. The top half of the page shows the Tool configuration, and the Run console appears on the first tab below. You can see detailed information for each step in the Tool as it runs.
Reviewing the error messages and codes provided during the test run is extremely important. These messages often contain specific details about what went wrong and where. By thoroughly analyzing test run errors, you can proactively resolve issues, optimize your Tool, and ensure it works as expected.
You can perform debugging for every step of your Tool, including the input and output, branches, lookups, and imports. Look for the blue T that designates a test run log as available for that step.
To view your test run errors:
-
Use the Test run button to run a test.
-
After completing your test, review the Run console to see where your errors occurred.
-
Click the error button or the blue T in the step to open the Test run errors window. In steps where only the blue T appears instead of the error indicator, you'll need to open the step first; then, use the View debug logs button to open the logs for the step.
-
Review your errors.
During the test run, the Run test button is replaced with a Cancel test run button. Click Cancel test run to abort the test run.
If a test run takes over 100 seconds, the system displays a message due to the long processing time. You can either cancel the run or wait for it to complete.
To avoid system performance issues, the test run will be auto-canceled in the following scenarios:
-
If the tool runs longer than two minutes
-
Uncaught exceptions
Test run data is automatically deleted in the following scenarios:
-
When your Celigo platform session expires
-
On running the next test in the same session
-
On navigating away from the Tool builder
-
On modifying any of the steps
Keep in mind these important tips to get started with test mode:
-
Always add mock response data to each destination step before you run your first test. Otherwise, dummy data will auto-populate the first run, which will not provide accurate test results. You can add mock response data either by...
-
Clicking Populate with live data inside a destination’s mock response panel (running the import can result in records being updated or created)
-
Entering your own data from the app’s API documentation (must include statusCode)
-
-
Test results will be cleared and are not saved if you navigate away from your tool, refresh, run a new test, modify the tool configuration.