The user should select the 'Other...' menu item from this menu, which will cause a wizard to be displayed with the various items that can be created. Within the list, there is a sub group with the title 'Choreography'. This group contains an entry called 'Scenario' that should be selected:

The user should then press the 'Next' button to see the following form:

This form enables the user to select both the folder, within which the new Scenario should be created (defaults to the folder previously chosen when invoking the context menu), and the name of the scenario (by default this is My.scenario).

When the 'Finish' button is pressed, a new Scenario file (with the specified name) will be created in the nominated folder. An editor will automatically be opened for the newly created Scenario.

The components within the scenario are:

Once the menu item is selected, it will the scenario to be simulated against the associated choreography description. Where a message event is valid, the send or receive icon will turn green.

Where an error is detected, the send or receive icon will turn red.

It is also possible to execute some services, while simulating others, using the 'Simulate and Execute' option from the menu above. When this menu item is selected, a popup window appears with the list of services. The services that should be executed can be ticked. Any services that are left un-checked will be monitored - by default all services are only monitored. To execute a service, the relevant Java generated extensions (and other dependencies) must be fully implemented and available.

When the 'Ok' button is pressed, this will cause the test scenario to be evaluated, which will produce an endpoint projection for each participant, create an endpoint monitor or runtime to operate on each of the endpoint descriptions, and then work through the list of message events defined in the scenario.

The information produced as a result of the execution of the test scenario is displayed in two different forms. The first window (the 'Scenaro Editor' tab) presents the elements of the test scenario as they are evaluated. If they complete successfully, they are displayed in green, otherwise they are shown in red. If an event group contains a message event that resulted in a failure, then it will also turn red (as in the image above).

The second form in which the results from the test scenario evaluation are presented are in the 'SImulation Log' tab. This information is presented as generated by the logging output from the scenario tester. This is in the form of INFO, WARNING and SEVERE (i.e. error) log messages.

To enable the user to identify which tracing output information is related to the element within the Scenario Results display, it is possible to select an item in the Scenario Editor and have the associated tracing output text for the selected item presented in the simulation log.

Log messages are recorded for both the test harness, as it works through the event groups and message events within a scenario, and also from the endpoint monitoring and runtime engines. The test harness produces three types of message, 'processing' to mark the start of processing a scenario element, and 'completed' or 'failed' to mark the end of a particular region of the test scenario (i.e. either the whole scenario, an event group or a particular message event). For example, the messages that would bound the processing of a particular message event would be:

INFO: <processing id="simplerfq-invalid/4/2" text="Message event" />

{other log messages from monitoring or runtime engine}

INFO: <completed id="simplerfq-invalid/4/2" text="Message handled" />

The id attribute in the log messages identifies the index to the relevant item within the scenario. In the above example, this indicates that the message event is in the fourth event group, and is the second message event within that group.

The other logging information, generated from the monitoring or runtime engines, provide tracing that will indicate: