The run-time environment
defines the plug-ins on which all other plug-ins depend. The run-time
environment is responsible for defining a structure for plug-ins and
the implementation detail behind them.
Blocked Action detection
The performance testing execution engine provides the capability
of detecting that an Action is blocked. The definition of blocked
is provided by the author of the Action. The definition is provided
as an amount of time an Engine Worker Thread is allowed to be unresponsive
in the course of executing the Action before it is considered blocked.
The performance testing execution engine logs the detection of blocked
actions at level FINEST in the Problem Determination Log. In the simplest
case, the run would be hung, and discovery of the blocked action would
come from examining the Problem Determination log after clicking Stop to end the run.
Extending subsystem management during a test run
A subsystem is a collection of classes in a discrete component
within the performance testing engine that provides a service to many
actions. For example, in test execution, the KernelWait subsystem manages think and sleep time for virtual users while a
test is running.
Extending initialization and finalization during a test run
You can specify code for your protocol to be executed by
the performance tester engine threads at strategic points during startup
and shutdown. For example, you can specify code to load libraries,
unload libraries, or perform other initialization or cleanup as required
by the protocol.
Public APIs for run time
The public APIs contain the public interfaces and classes
that you can use to extend the run-time environment functionality.