Load testing

Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

Checks for memory leaks or other problems that may occur with prolonged execution.

Confirming that all business processes complete properly while the server(s) handle concurrent usage.

Java 2 Enterprise Edition - The J2EE platform manages the infrastructure and supports the Web services to enable development of secure, robust, and interoperable business applications.

Any deployable unit of J2EE functionality. This can be a single module or a group of modules packaged into an .ear file with a J2EE application deployment descriptor. J2EE applications are typically engineered to be distributed across multiple computing tiers.

A function of the Topaz for J2EE application, which enables the time a transaction, spends on a J2EE-compliant application server to be broken down and analysed.

A Topaz profile that contains the data sent from the J2EE probes. J2EE profiles are defined in the Topaz Monitor Configuration.

The elements that define a load test, such as virtual users, scripts, host machine, run time settings, results location.

An end-to-end (browser to backend to browser) measurement of one or more user actions within an action file.

Testing conducted to evaluate the compliance of a system or component with specified performance requirements. [IEEE]

Performance testing focused on ensuring the application under test gracefully handles increases in work load.

Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.

Testing whether the system meets its specified storage objectives.

Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements. [IEEE]

Any series of steps that an end user performs in an application, whose performance you want to monitor. Transactions are recorded using Topaz recording tools and saved in transaction files. When replayed, transaction response time and availability data is collected. You view transaction performance data from the Topaz Web site.

The state of a transaction - Transactions that complete (pass) are considered available; transactions that do not complete (fail) are considered not available.

A function of Topaz that enables transaction response time data to be broken down and viewed according to time spent on the network, server, and client.

A state describing a transaction that does not complete its run, either due to error or time-out.

The time it takes for a pre-recorded transaction to be completed.

One or more recorded action files that, when played back, emulate a real user performing the actions.

Testing where the system is subjected to large volumes of data.