Here information is provided about the terms which are used in Stress Module of PruTAN.

Lists of Terms :

1. Mode(Volume)
2. Mode(Duration)
3. Benchmark(Constant)
4. Benchmark(Ramp Up)
5. Benchmark(Spike)
6. Virtual Users, Volume(Per Second), TimeOut, Delay, WarmUp, Start After, Request Per User, Execution TimeOut,RampUp Period, Spike User, Spike Interval, Hold Spike For, Increment value, Starting Value, Max Value
7. Add Scripts , Add Buckets

Mode(Volume) :

Definition:

Volume testing involves assessing the system's ability to handle a large amount of data or a high transaction volume.

Objective:

The primary goal of volume testing is to ensure that the system can effectively manage and process a significant amount of data without performance degradation or data loss.

Example:

In a database system, volume testing might involve inserting a large number of records to evaluate how the system handles the data storage and retrieval process.

Mode(Duration) :

Definition:

Duration testing, also known as endurance testing, focuses on evaluating the system's stability and performance over an extended period.

Objective:

The main aim of duration testing is to identify any issues related to resource leaks, memory management problems, or other gradual degradation of system performance over time.

Example:

In an e-commerce application, duration testing might involve simulating continuous user interactions over an extended period to ensure that the system remains stable without accumulating errors or slowing down.

Benchmark(Constant) :

Definition:

Constant load, in stress testing, involves maintaining a steady and continuous level of stress on the system for an extended period.

Usage:

This scenario helps assess how well the system performs and whether it can sustain a consistent level of load without degradation over time.

Benchmark(Ramp Up) :

Definition:

Ramp up in stress testing involves gradually increasing the load on the system over time.

Usage:

This scenario is useful for identifying the system's breaking point or the threshold at which it starts to exhibit performance issues. It helps determine how the system scales with increasing levels of load.

Benchmark(Spike) :

Definition:

Spike testing introduces sudden and significant increases in load on the system for a short duration.

Usage:

This scenario helps evaluate how well the system handles sudden bursts of activity, simulating real-world scenarios where there is a sudden surge in user activity. It assesses the system's ability to quickly adapt and recover from rapid increases in load.

Virtual Users:

Virtual Users are simulated users or entities that emulate real users interacting with a software application. They are used in performance testing to simulate concurrent user activity and assess how well the system can handle a certain load.

Loop Count:

Loop Count refers to the number of times a set of actions or transactions is repeated by a virtual user during a performance test. It helps simulate repeated usage patterns and assess the system's behavior over multiple iterations.

TimeOut:

Timeout is the maximum allowable time a request is given to execute. If the system takes longer than the specified timeout period, the request may be considered failed.

Delay:

Delay, in the context of performance testing, is a pause or wait time introduced between execution or transactions performed by a virtual user. It helps simulate realistic user behavior and assess system response times under varied conditions.

WarmUp:

Warm-Up is the initial period of a performance test where the load on the system gradually increases. It allows the system to reach a stable state before collecting performance metrics. This phase helps identify and eliminate initial performance anomalies.

Start After:

Start After is a configuration setting that specifies a delay before a virtual user or a group of virtual users begins executing their actions. It allows for staggered or phased starts, simulating a more realistic user arrival pattern.

Execution TimeOut:

Execution Timeout is the maximum duration allowed for the execution of a specific task, action, or transaction. If the task takes longer than the specified timeout, it may be considered unsuccessful or result in an error.

Ramp-Up Period:

The duration over which virtual users are gradually added to the test at the beginning. It's a gradual increase in the load over time, allowing the system to reach the desired level of load smoothly rather than all at once.

Spike User:

A sudden, temporary increase in the number of virtual users during a stress test. This spike is used to simulate sudden bursts of user activity on the system, helping to evaluate how the system responds to unexpected surges in traffic.

Spike Interval:

The time period between each spike in the number of virtual users during a stress test. It determines how frequently the system experiences sudden increases in load.

Hold Spike For:

The duration for which the spike in the number of virtual users is sustained during a stress test. It defines how long the system is subjected to the increased load caused by the spike.

Increment Value:

The amount by which the load is increased at each interval during the ramp-up period of a stress test. It determines the rate at which virtual users are added to the test.

Starting Value:

The initial number of virtual users at the beginning of the test before any ramp-up or spikes occur. It sets the baseline load level from which the stress test begins.

Max Value:

The maximum number of virtual users that will be reached during the stress test. It defines the highest load level that the system will be subjected to during the test.

Add Scripts:

In Add Scripts we add scripts which has to execute for testing. User can add multiple scripts or even collections. Note : Collections or scripts reflected here are created in API module.

Add Bucket:

In Add Bucket feature we can add execution time buckets so the scripts which take different time will fall in that bucket's time period.User can add as many bucket as it needed.