Event Name

Description

Short Info

Long Info

Abort

This event ends a test in a "cannot finish" state. It is a failing type of end event.

Event Aborted

Assert evaluated

A non-embedded assertion will generate this event if it does not fire. These events are the assertions that did not get to execute their consequence.

The name of the assertion

Assertion fired

A non-embedded assertion will generate this event if it does fire. Firing means it is true and its consequence will be followed.

The name of the assertion

The log message of the assertion, or a DevTest-generated message if there is no log message set

Call made

Steps that perform object calls like web services or EJBs use this event to report each call that is made on the object.

The name of the step

The call as a string, for example, void setName( java.lang.String name[Basic Checking] )

Call result

Steps that perform object calls like web services or EJBs use this event to report the response they get from calls.

The name of the step

The call response as a string. If the response is an object, then an XML view of the object is shown.

Configure for load test

Configure for load test

The test run has been configured as a load test. Selecting individual events has been disabled.

Coordinator ended

A coordinator has been removed.

The name of the coordinator server

Coordinator server ended

The coordinator server was ended.

The name of the coordinator server

Coordinator server started

The coordinator server was created.

The name of the coordinator server

Coordinator started

A new coordinator was created.

The name of the coordinator server

Cycle ended normally

The test execution completed in a successful state.

The name of the test case

Cycle ending

The instances have been instructed to stop testing.

Cycle failed

The test execution failed. That there are no exceptions in the test case, but either logic errors in the test case or in the system under test caused the test case not to complete as expected.

The name of the test case

Cycle history

Every model that runs will generate one of these events. It is the final trace of all the details of its run.

Cycle History

Cycle initialized

The test has been initialized (loaded).

The name of the test case

Cycle runtime error

An abnormal DevTest error occurred. For example, the coordinator lost its connection to a simulator while running a test.

Varies but it is usually the name of the test element (step, data set, or filter) that has the error

Usually a message that explains the error

Cycle started

This test instance and cycle have just started.

The name of the test case

Data set read

Data sets generate an event that makes it clear what values are about to be used.

Data set read

HTTP performance

This event is generated for every HTTP transaction that DevTest executes to capture the performance statistics.

HTTP performance statistics

Info message

Basic logging data. For example, the HTTP/HTML request step sends this message with the step name in the short field and the URL being sent to the server in the long field.

Usually the name of the step during which this message was generated

Usually a message that DevTest generated

Instance ended

Sent when a simulator instance has finished.

The name of the simulator

Instance started

Sent when a simulator creates an instance.

The name of the simulator

Log message

Basic logging data. Can be turned off to minimize overhead when filtering events.

The message sent to the log

Metric alert

A metric has been collected and is reporting its value.

The short name of the metric, for example, DevTest: Avg Response Time

The value of the metric collected

Metric started

Metrics that are collected generate real-time events of their values.

Metric Started

Metric value

Metrics that are collected generate real-time events of their values.

Metric value

Model definition error

A test case error was discovered during execution of the test. For example, the name is constructed from a property that does not exist.

Varies but it is usually the name of the test element (step, data set, or filter) that has the error

Usually a message that explains the error

Pathfinder

The system being tested has DevTest integration enabled. This event contains the DevTest integration XML data that was captured.

The name of the step

The XML representation of the DevTest Integration data captured

Property removed

A property was removed.

The property key

The word "<removed>"

Property set

A property was set.

The property key

The property value

Simulator ended

Sent when a simulator has ended.

The name of the simulator

Simulator started

Sent when a simulator has started.

The name of the simulator

Step bandwidth consumed

Approximate amount of data sent and received from the system under test for the step execution.

The name of the step

Actual number of bytes read/received

Step error

An error has occurred in the system under test. For example, there was no response from a web server. This event is for a step. The EVENT_TESTFAILED refers to the complete test case.

The name of the step

If available, a message to help determine the cause of the failure

Step history

Every step has a history event that fires of type com.itko.lisa.test.NodeExecHistory in its long info.

Step history

Step request

Steps that support this event use it to report the actual request made to the system under test.

The name of the step

The request data as a string

Step request bandwidth

Step response

A step was completed against the system under test.

The name of the step

The response data as a string

Step response bandwidth

Step response time

The amount of time a step took to execute against the system under test.

The name of the step

The number of milliseconds to execute the step

Step started

A step is being executed.

The name of the step

Step target

Every step has a target, such as the URL for a web request or the JNDI name of an EJB.

Step warning

A warning was recorded. For example, a filter took the default value because it could not find the current value.

Step warning

Subprocess finished

A subprocess has finished executing.

Subprocess ran

A subprocess has started.

Suite aborted

When a setup test (defined in a suite document) has failed, then the suite will not run the tests defined in the suite. This event indicates that this happened.

The name of the suite

Suite ended

All the tests running as part of a suite have finished.

The name of the suite

Suite history

Every suite that runs will generate one of these events. It is the final trace of all the details of its run.

Suite History

Suite setup/teardown

The suite has a setup or teardown test defined and that test has just started to run.

The name of the suite

The name of the test, path to the test, and other information

Suite started

A suite is starting to run.

The name of the suite

Suite test failed

A test running as part of a suite ended in failure.

The name of the suite

Suite test passed

A test running as part of a suite ended successfully.

The name of the suite

Suite test staged

A test is staged to run as part of a suite.

The name of the suite

The name of the test, path to the test, and other information

Test ended

Sent when the coordinator stops the test.

The name of the test case

Test not active

A test in a suite is marked as inactive.

Event Test Not Active

Test started

Sent when the coordinator starts the test.

The name of the test case

VS log message

VSE internal logging

VS log message

VS no transaction match

A virtual service did not match a transaction request to at least one recorded response.

VS transaction no match

VS service ended

A virtual service was stopped.

VS service stopped

VS service started

A virtual service was started.

VS service started

VS transaction finished

A virtual service finished processing a transaction request.

VS transaction match

A virtual service matched a transaction request to at least one recorded response.

VS transaction match

VSE server reset

A service reset request was made of a server.

VSE server resets

VSE server shutdown

A virtual service environment was asked to shut down.

VSE server shutdown

VSE server stop

A service stop request was made of a server.

VSE server stops