Test Console

this only applies at the action level the turbine canvas includes a test console within the playbook canvas, allowing end to end testing of trigger flows this console displays each automation step to indicate whether a run succeeds or fails you can test using real data or custom test data, offering a flexible environment for playbook verification accessing the test console to open the test console, click the test icon on the playbook canvas understanding the test console layout after opening the test console, you’ll see the flow being tested on the left side this layout provides a clear view of each automation step to the right, there are two main tabs runs displays the date and timestamp for each test run, indicating whether it was successful or failed test data allows input modification for custom testing icons next to each run provide a quick status icon description indicates a failed test indicates a successful test example of a successful test run in this example, the test console displays a successful run of flow 1 on january 8, 2024, at 4 44 pm (utc) for additional metadata about the flow and individual steps, such as trigger data, action data, and published results, expand each section using the collapse icons if a run is marked with test , it indicates a console test run example of a failed test run in this example, flow 1 has failed the console shows a detailed view at january 8, 2024, 7 20 pm (utc) to investigate the failure, scroll down to the step with the fail status and expand it for more information failed action view in the expanded view, the message field provides specific information to help identify and resolve the issue failure message running tests with custom data to test with modified data, select the test data tab and adjust inputs you can also use the run again button to re run the test the event dropdown defaults to the most recent event, but you can select past events for testing historical scenarios for custom data, select custom json in the data source dropdown this opens a blank text editor where you can enter custom json for testing test data tab with custom json after modifying data, click test to execute the updated run navigate back to the runs tab to view the results of the most recent test testing with record event triggers for flows that use a record event trigger , the test console provides the option to test with historical events by selecting previously processed records this feature is beneficial for verifying the playbook's behavior with data that has been processed before, ensuring that any changes to the flow work as expected in real world scenarios in the test data tab, a list of historical records is displayed with columns such as tracking id , time created , ip , and correlation you can filter these columns by clicking on the filter icon and selecting the desired columns, as shown in the image below record event trigger with historical records to run the test select the record you want to use for testing by clicking the radio button next to the tracking id click test to initiate the flow with the selected historical record data note you cannot directly modify the record data for these tests the test console will use the selected record exactly as it was originally processed this functionality is useful for debugging, troubleshooting, and validating flow behavior with actual historical data, ensuring the playbook operates correctly across different scenarios the test console in turbine canvas allows for flexible testing with both real data and custom data for cases where specific inputs are needed for the test, you can configure and run the playbook with custom json as the input using custom json in the test console open the test console click the test console icon on the playbook canvas to open the console select custom json as the data source enter custom json data in the json editor, enter the specific data you want to test with this data should match the expected input format for your playbook for example, if your playbook requires a specific payload structure, you can define it here to simulate that scenario run the test after entering the json data, click the test button to execute the playbook with the specified input the playbook will process this custom input, and the results can be observed in the runs tab review the results go to the runs tab to view the output of the playbook with your custom json input you can expand each step in the flow to verify that the playbook processes the data as expected clear or modify json data if you need to make adjustments, you can edit the json directly in the editor or use the clear text editor link to reset the input closing the test console to close the test console and return to a full canvas view, click the x icon in the upper right corner