The ITEX Simulator (in Windows)

This chapter describes the ITEX Simulator in the Windows version of ITEX. It gives an introduction to the concept of the ITEX Simulator, as well as a guide to its functionality.

Note:  Windows version This is the Windows version of the chapter. The UNIX version is The ITEX Simulator (on UNIX)

Table of Contents 

• The Simulator
• Performing a Simulation
• The ITEX Simulator Operations
• Information Messages
• Informative Messages
• Warning Messages
• Error Messages
• Troubleshooting
• The Simulators Stop Communicating
• Test Execution Stops
• The Simulators Get Out of Sync
• Type Mappings in Co-Simulation

The Simulator

The ITEX Simulator allows you to generate executable test suites (ETS) for testing of simulated SDT systems. This allows the testing of the system design early in the design process.

These ETSs allow you to execute test cases and/or test groups (hereafter referred to as tests) at full speed or by single stepping through the selected tests. There is also the possibility to set breakpoints in the tables of the tests.

It should be noted that there is no separate ITEX Simulator GUI. The ITEX Simulator will use the Table Editor to present the current line during execution.

More information about the Simulator in SDT can be found in The SDT Simulator.

Performing a Simulation

Given a test suite containing a set of tests you want to execute together with a simulated SDT system, the following steps are to be performed:

1. In ITEX, analyze the test suite and make sure it contains no errors.
2. In the ITEX CCG Settings dialog, generate an executable test suite.

The following C Code Generator Options should be set:

• Generate Simulation Kernel
• Ignore bodies of test suite operations
In the Build Options tab:

• You should set Run Make.
• You may have to change the Makefile Type.

Start the ITEX Simulator by selecting Invoke Simulator from the Simulate menu. In the file dialog that will be issued, select the simulator ETS -- that is, the executable produced in step 2. After that, the Simulator toolbar will appear.

4. Generate and start the SDT Simulator, if not already done. In the SDT Simulator UI, load the SDT generated simulator executable.
5. In the SDT Simulator, give the commands start-itex and then go-forever.
6. In the ITEX Browser, select the tests you wish to execute.
7. Click the Run/Continue or Step button, to start the actual simulation in ITEX.

The ITEX Simulator Operations

	To abort the test in progress: Select Simulate > Abort. The SDT Simulator may have to be restarted after this step. A new simulation can be started now.
	To temporarily pause the test simulation: Select Simulate > Pause. The simulation can be continued by doing a "run" or "step" operation.
	To step one line of TTCN code: Select Simulate > Step.
	To run/continue a test at full speed until it is finished or until a breakpoint is reached: Select Simulate > Run/Continue.
	To toggle breakpoint status at currently selected lines in the Table Editor: Select Simulate > Toggle Breakpoint.

Information Messages

The Simulator can present messages to the user in three forms:

• Informative messages
• Warning messages
• Error messages

Informative Messages

Informative messages are normally presented at the status bar. These might be for instance progress reports or other simple messages, which are only of a temporary interest (such as the tool tips).

Warning Messages

Warnings, also known as "non-critical errors", are events that indicate a problem during the preparation for a simulation, or during the actual simulation run. These are presented in standard warning dialogs.

Error Messages

Critical errors will halt the simulation. They are presented by an error dialog that appears in front of the application. The error dialog can often appear large and intimidating, but it simply gives a more verbose reason to why the error occurred, and what steps should be taken to avoid it.

Troubleshooting

The Simulators Stop Communicating

The SDT Simulator and the ITEX Simulator may stop communicating. This can occur if there are "old" instances of the Simulator ETS process still alive. They will then "steal" messages from the intended recipient. There are some ways to make the Simulators communicate again:

• Exit the ITEX Simulator and start it again.
• Exit the ITEX Simulator. Restart the SDT Simulator. Start the ITEX Simulator again.
• Exit the simulators and the Organizer. Check that no Postmaster process and no ITEX Simulator ETS process remains. If they do, kill them. Start the Organizer, the SDT Simulator and the ITEX Simulator.

Test Execution Stops

The execution of tests may stop at a certain point during execution for no reason. If the problem is reproducible, you should check the supported types. There is a possibility that a type has been used in a message between the simulators that is not supported.

The Simulators Get Out of Sync

The Simulators may get out of sync. One way of doing this is when an execution in the ITEX Simulator has been aborted and the SDT Simulator has not been restarted.

• Press the abort button in the ITEX Simulator. Restart the SDT simulator.

Type Mappings in Co-Simulation

The data type mapping used by the co-simulation of the SDT and ITEX simulators in Windows is the same as for the co-simulation on UNIX. See Type Mappings in Co-Simulation.