Page History

Creating test events

The The Editor-Debugger utility is capable of generating can use test events chosen specified by the user and generated by the utility to help debug the scripts. Test events are not registered by the video surveillance system, i. e. they are not listed in the events log and not it means they aren't displayed in the Event Viewer and aren't saved to the database.

No more than one test event can be created for each script.

...

1. In the Debug and edit menu, select Edit test event, or click the  button in the toolbar.
2. The Test message window will open.  
   Image Removed
   This window is used for entering the parameters of a test event parameters.
   Image Added
3. Enter the following information in the fields of the Test message window:
   
   1. SourceType – —system object type;
   2. SourceId – —system object identification number;
   3. SourceAction – the —event generated by the specified system object;
   4. param – —additional event parameters;
   5. value – —values of the additional parameters.
      

      Info
      title Note
      The main system objects, their events and parameters are described in Description of events and reactions of system objects. You can also get them using the ddi.exe utility (see Getting the list of system names of objects, reactions and events in Intellect).

4. When you filled in the fields of the Test message window, click the Click the OK button.

The test event is now created.

The created test event will be displayed in the Event field in a special string format.

Figure The figure below shows the test event example: “Arm Arm Camera 111”111.

 Running a script with a test event

To run the script with a test event, do one of the following:

1. Click the Test run Image Added button in the toolbar.
2. In the Debug and edit menu, select Test run.
3. In the Debug and edit menu, select Test run in third-party debugger.

When you select the Test run in third-party debugger option, the third-party debugger starts to run the test (see Using third-party debugger programs).

The results of the verification and execution of the script are displayed in the corresponding debugging window of the Editor-Debugger utility.