[LoadRunner] The controller of the first knowledge of LoadRunner12

In the previous chapter, using the Vugen recording script, you would then use a controller to provide a test scenario for the recorded script.

Introduce some simple uses of controller in this chapter

2. Open the previously recorded script in Vugen, click Tools-create Controller Scenario Create a scene with an existing script
   
4. Controller's scene is divided into two kinds
   
   • Target scenario (Goal oriented Scenario): The main test script can meet a certain standard
   • Manual Scene (Manual Scenario): Long multi-state run scripts view performance bottlenecks
     
6. First introduce the target scene, there are 2 tabs below the interface, where design is mainly the configuration of the scene, the Run tab is the state of the runtime, switch to the Design tab and click Edit Scenario goal at the bottom left of the interface to choose a test scenario, The LoadRunner provides 5 test scenarios by default and allows users to define different scenarios and values based on the goals of the test
   
   • Virtual User: Specify the number of concurrent virtualized users
   • Hits per Second: Specify the number of hits per second
   • Transactions per Second: Specifies the number of transactions per second
   • Transaction Response Time: Specify response times for each transaction
   • Pages per Minute: Specify the number of pages viewed per minute
     
8. Back to the Design tab, click the Run-time Settings button in the middle of the interface to make some running settings, such as whether each virtual user is running in a process or thread, and if each script is automatically defined as a transaction. It is recommended that you run the virtual user as a thread and do not define the script as a transaction but manually add the transaction to the script
   
10. In the table at the top left of the Design tab, you can add a script,% of target specifies the percentage of users that are allocated the runtime, and Load generators is a policy that assigns virtual users to different computers when testing multiple computers
    
12. The Design tab of the manual scene is the same on most interfaces and the target scene, and the table at the top left can be changed quantity to% of target by Scenario-convert Scenario to the Percentage mode.
14. The scene configuration of the manual scene provides 4 options for users to get an ideal test scenario by customizing each option
    
    • Initialize: Virtual user initialization option, you can choose to initialize all virtual users at the same time, each time too long to initialize several virtual users and initialize the user only before each virtual user runs
      
    • Start Vusers: Set the number of users, specify the number of virtual users, and choose to start all virtual users directly or to start several virtual users for too long
      
    • Duration: Set run time, you can choose a fixed run time or stop running after each user execution (at this point you can set the number of iterations of the script through the Run-time settings in iterations)
      
    • Stop vusers: Virtual User Recycling policy, options with virtual user initialization settings
      
16. Once the scene is set up to run, the runtime automatically switches to the Run tab, where each script runs at the top left of the Run tab, and the top right shows some information about the entire scene, such as the number of virtual users currently running, the run time, the number of successful transactions, the number of failed transactions, the number of errors, and so on. Click to view specific details
    

After the final wait for the scene to run, a test is completed, and the results of using analysis to view and analyze the script are described.

Ps: There are many features in the controller, such as virtual IP and load generators on multiple machines to expand the test environment, in this article is not described in detail, interested friends can search by themselves.

[LoadRunner] The controller of the first knowledge of LoadRunner12