Loading entities and submitting events from Insight Designer

In Insight Designer, you can initialize entities, send a sequence of events to verify whether a situation is detected, and write tests that can check entities and entity attributes. The entities and events are stored in a set of files so that you can repeat and modify the tests as many times as you need.

Tip: In between your test runs, you might want to reset the server. If you do not reset the server, the previous state of the agents remains in operation. Agents are not removed by the system so that in production rules can be updated in a continuous fashion. When you debug a solution however, a single test is sufficient and in most cases you reset the server between tests to get a fresh start.
  1. Creating common definitions
    You can create a set of definitions that can be used by entity loaders, event sequences, and other common definitions. A common definitions is stored in a test client project; there is no limit to the number of common definitions that you can have in the Common Definitions folder.
  2. Creating entity loaders
    The entity loader editor provides access to the BOM vocabulary. You define the entities from your solution BOM project that you want to load by writing a set of constructs. Once defined, an entity with a specific entity ID can only be loaded once.
  3. Running entity loaders
    When the entity definitions are complete, you can load the entities to a started server.
  4. Creating event sequences
    An event sequence is used to define a set of test events that you can run against your solution. The events are sent in the order in which they are defined in the file.
  5. Running event sequences
    When the event sequence is complete, you can submit the event sequence to a running development server.
  6. Creating test scenarios
    In test scenarios, you list the entity loaders and event sequences that you want to load and submit. You can also write tests that check the values of entities and entity attributes. If you expect a certain result from a scenario, checking the value of an entity against this expected result can be a useful way to validate that the solution works correctly.
  7. 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.
Parent topic: Testing solutions
Related reference:
Test language syntax