HP Diagnostics

HP Diagnostics falls into the middle ground between Quality Assurance and Operations Performance Validation.

For developers, having Diagnostics means that tracing code doesn’t have to be added and removed. This is a big side effect of why diagnostics can improve performance.

Diagnostics is the science of pinpointing the root cause of a problem. LoadRunner is the first load testing tool to provide a set of Diagnostics modules that trace, time, and troubleshoot end-user transactions across all tiers of the system. These modules extend LoadRunner to provide a unified view of both end-user experience and application component (method, SQL) level performance. The intuitive visual interface allows the user to drill down from a problematic business process all the way to the poorly performing component. This granularity of results ensures that every load test provides development with actionable results, thus reducing the cost and time required to optimize J2EE/.NET applications.

Diagnostics for J2EE/.NET provides complete visibility into the transaction performance of J2EE/.NET- based applications. Users can drill-down from a poorly performing end user transaction and view JNDI, web, EJB, and JDBC performance. Having identified the top-time layer, users can further drill-down to the Method or SQL level and pinpoint the slow SQL query or method impacting the end-user. This granularity of results data ensures that every load test provides development with actionable results thus reducing the cost and time required to optimize J2EE/.NET applications.

Probe Profiler Tabs

Summary

• Memory
• Load
• Shortest Requests

Hotspots

• Slowest Methods
• CPU Hotspots (Methods)
• Slowest SQL

Metrics

• System (Host) CPU, Memory Usage, PageInsPerSec, PageOutsPerSec, PageOutsPerSec, Disk, Network
• JVM: Probe: HeapFree, HeapTotal, HeapUsed
• Java Platform: Classes, GC, Threads
• Mercury System
• WebLogic: EJB, Execute Queues, JDBC, etc.

Threads (JVM 1.5)

All Methods

All SQL

Collections (using LWMD)

Exceptions

Server Requests

Web Services

Controller

You use the LoadRunner Controller to manage and maintain your scenarios. Using the Controller, you control all the Vusers in a scenario from a single workstation.

Creating the Scenario

A scenario describes the events that occur during a testing session. A scenario includes a list of machines on which Vusers run a list of scripts that the Vusers run, and a specified number of Vusers or Vuser groups that run during the scenario. You create scenarios using the LoadRunner Controller.

Creating a Manual Scenario

You create a scenario by defining Vuser groups to which you assign a quantity of individual Vusers, Vuser scripts, and load generators to run the scripts.
You can also create a scenario using the Percentage Mode, in which you define the total number of Vusers to be used in the scenario, and the load generator machines and percentage of the total number of Vusers to be assigned to each Vuser script.

Creating a Goal-Oriented Scenario

For Web tests, you can create a goal-oriented scenario, in which you define the goals you want your test to achieve. LoadRunner automatically builds a scenario for you, based on these goals.

Creating Sample Scenario

1. Launch LoadRunner
2. Under Load Testing tab, select Run Load Tests

3. To manage your load test by specifying the number of virtual users to run, select Scenario type as Manual Scenario

4. Add scripts to scenario and click Ok.

5. Look at the Scenario Groups, here you can add more scripts, edit Vusers quantity, add load generators, edit Runtimes Settings.

6. Then work on Scenario Schedule, specify Schedule name, according to test plan Choose Schedule type , and Run Mode

7. Then work on Global Schedule, keep properties for Initialize as it is.
8. Set Start Vusers properties depending on the ramp up required.
9. Specify Duration of test run.
10. Set Stop Vusers properties depending on the ramp down required.

11. You can see the graphical representation of the created scenario.

12. When you are done with Scenario Design part click on Run which is located at bottom of the page.
13. To add Windows Resources go to Available Graphs, Under System Resource Graphs, choose Windows Resources

14. To add Measurements, right click on Windows Resources, and choose Add Measurements.
15. In the Windows Resources pop-up, click on Add button, in the new pop-up specify Machine Information, like name and platform.

16. Select the Resource Measurements and click on add button, and add the resource.
17. Click on Start Scenario.
18. Now controller will start running your designed scenario.
19. When test is running you can monitor the Windows Resources and Test Status with respect to Transactions passed, failed and Errors occurred while running.

20. You can see the detail status of transaction passed and failed by click on mirror right next to Passed Transactions and Failed Transactions

21. You can see the errors thrown by web app by clicking on mirror right next to Errors

22. While test is running, if you want to Add Vusers, you can do that by clicking on Add Vusers Tab.
23. Select group name, quantity to add, load generators name and script name.
24. You can see the Test results by clicking on Analysis icon.