Running test scenarios

After you create a test scenario, you can run the file on a started server. All of the entities, events, and tests that you define are submitted to the server and the results are printed in the Console tab.

Before you begin

Before you begin, you must have a deployment configuration and a completed test scenario.

About this task

Running a test scenario on a server is a quick way to validate that the events and entities in your solution are working as you expect. You can run any number of test scenarios on a server, and easily modify and run any test scenario again if necessary.

You can customize how the test scenario runs. You can record the results of a test scenario to visualize them in Insight Inspector, pause between steps in a test scenario so that you can manually check the state of your entities, and decide whether to allow pending schedules to run. You can also pause the processing of events step by step to check the results in the log. After you run a test scenario once, you can rerun a fresh instance of your test scenario or rerun the existing solution state.

Procedure

Right-click the test scenario and select Run as > Test Scenario.
In the Run Configurations wizard, confirm that your test client project and test scenario information is correct.
Optional: Click Reset solution state to reset the rule agent history, cached engines, time triggers, pending changes, and global aggregates on your server before the test scenario is run.
Optional: If you want to clear all existing entities from the server before the test scenario is run, select Reset solution state and Delete all entities.
Optional: Click Enable recording to record the events running on the server. If you select this option, you can later review the behavior of your events in Insight Inspector.
Optional: Click Pause between steps to pause processing after each step in the test scenario. After you run a test scenario with this option selected, you can check the state of your solution after each step in your test in the server logs, in the map viewer, or by using the REST API. To continue processing step by step, press Enter in the Console tab.
Optional: Clear Trigger pending schedules if you do not want to process pending schedules after the last step in the test scenario. Trigger pending schedules causes any processing that is scheduled after the last step in the test scenario to be triggered immediately.
Click Run.

Results

The test scenario stops when it reaches a test that fails. The result of your test displays in the Console view. Examine the tests that failed or do not behave as expected to understand why the actual values are not what you expect. You can modify and run a scenario as many times as you need to ensure that the entities that you are checking pass the test.