• RSS
  • Facebook
  • Twitter

One Center for all the Testing Need. OneTestingCenter is for all, for all QA, for all Automation. Automation is easy, fun and enriching experience. Happy Learning and Happy Testing!

  • Access to All QA

    At OneTestingCenter, you find lots of books,articles,blogs and detailed guides. Everyone has access to QA. Happy Learning, Happy Testing.

  • Global Trainings

    All the QA/Auotmation trainings are available at OneTestingCenter. QA, Automation, QTP/UFT, Selenium, LoadRunner, QC/ALM, Appium...

  • Automation Learning Fun

    Technology is always evolving. Automation is always challenging. To be frank, Automation is fun, enthusiastic and enrching experience.

    Load Runner Terms and Definitions:

    o   VUsers
    o   VUser Generator
    o   Controller
    o   Analysis
    o   Scenarios
    o   Transactions
    o   Benchmark
    o   Throughput
    o   Bottleneck
    o   Ramp up
    o   Rendezvous point
    o   Paramertization
    o   Checkpoints

    o   VUsers:
    o   Vusers are the Virtual Users that act as similar as real  users (real human beings)

    o   VUser Generator
    o   Tool that creates Vuser script such that it can be run for any number of Vusers

    o   Controller
    o   Tool to manage / control all the Vuser scripts or the load test scenarios

    o   Analysis
    o   Tool to analyze the load test results such that to view and take decisions

    o   Scenarios:
    o   A scenario is the combination of Load test scripts , Vusers , Performance conditions, Servers and so…
    o   A scenario defines the events that occur during each testing session.
    o   For example, a scenario defines and controls the number of users to emulate, the actions to be performed, and the  servers/machines on which the virtual users run their emulations.

    o   Transactions
    o   Transactions are the actions that are performed by the application/test during test execution
    o   Measured event (i.e. Time it takes to return data to a screen after a QUERY button is pressed)

    o   Benchmark
    o   Benchmark is the ideal business need.
    o   It’s well defined customer need like number of Vusers to act up on, no # of transactions per minute , no # of bits transfer rate/sec

    o   Throughput
    o   Throughput is the average rate of successful message delivery over a communication channel.
    o   The throughput is usually measured in bits per second (bit/s or bps)


    o   Ramp up
    o   Facility to gradually increase the amount of Vusers/load on the server

    o   Bottleneck
    o   Bottleneck is the  maximum limit over benchmark needs
    o   Bottleneck is the extended benchmark need
    o   No# Vusers that the application supports at max
    o   No# transactions that the application supports at max

    o   Transaction start and end points:
    o   Transaction start point is the time at which the transactions (actions) are begun
    o   Transaction end point is the time at which the transactions (actions) are ended

    o   Think Time
    o   Think time is the time that a real user waits between actions

    o   Rendezvous point:
    o   Rendezvous point is the waiting point (pause point) that instructs Vusers to wait during test execution until the multiple Vusers to arrive at that point, in order that they may simultaneously perform a task.
    o   For example, to emulate peak load on the bank server, you can insert a rendezvous point instructing 100 Vusers to deposit cash into their accounts at the same time.

    Reactions:

    Load Runner Terms and Definitions:

    Load Runner Terms and Definitions:

    o   VUsers
    o   VUser Generator
    o   Controller
    o   Analysis
    o   Scenarios
    o   Transactions
    o   Benchmark
    o   Throughput
    o   Bottleneck
    o   Ramp up
    o   Rendezvous point
    o   Paramertization
    o   Checkpoints

    o   VUsers:
    o   Vusers are the Virtual Users that act as similar as real  users (real human beings)

    o   VUser Generator
    o   Tool that creates Vuser script such that it can be run for any number of Vusers

    o   Controller
    o   Tool to manage / control all the Vuser scripts or the load test scenarios

    o   Analysis
    o   Tool to analyze the load test results such that to view and take decisions

    o   Scenarios:
    o   A scenario is the combination of Load test scripts , Vusers , Performance conditions, Servers and so…
    o   A scenario defines the events that occur during each testing session.
    o   For example, a scenario defines and controls the number of users to emulate, the actions to be performed, and the  servers/machines on which the virtual users run their emulations.

    o   Transactions
    o   Transactions are the actions that are performed by the application/test during test execution
    o   Measured event (i.e. Time it takes to return data to a screen after a QUERY button is pressed)

    o   Benchmark
    o   Benchmark is the ideal business need.
    o   It’s well defined customer need like number of Vusers to act up on, no # of transactions per minute , no # of bits transfer rate/sec

    o   Throughput
    o   Throughput is the average rate of successful message delivery over a communication channel.
    o   The throughput is usually measured in bits per second (bit/s or bps)


    o   Ramp up
    o   Facility to gradually increase the amount of Vusers/load on the server

    o   Bottleneck
    o   Bottleneck is the  maximum limit over benchmark needs
    o   Bottleneck is the extended benchmark need
    o   No# Vusers that the application supports at max
    o   No# transactions that the application supports at max

    o   Transaction start and end points:
    o   Transaction start point is the time at which the transactions (actions) are begun
    o   Transaction end point is the time at which the transactions (actions) are ended

    o   Think Time
    o   Think time is the time that a real user waits between actions

    o   Rendezvous point:
    o   Rendezvous point is the waiting point (pause point) that instructs Vusers to wait during test execution until the multiple Vusers to arrive at that point, in order that they may simultaneously perform a task.
    o   For example, to emulate peak load on the bank server, you can insert a rendezvous point instructing 100 Vusers to deposit cash into their accounts at the same time.