1. 1 Copyright © 2011 Tata Consultancy Services Limited PERFORMANCE TESTING

2. 2 Group members 834906 - Saurabh Menon 830894 - Kiran Mayekar 850316 - Nikhil Sonawane 858064 - Akshay Saxena 838927 - Nupur Shah 831314 - Pooja Singh

3. 3 Performance Testing  Performance testing is the process of determining the speed or effectiveness of a computer,network,software program or device  Without Performance testing,Software is likely to suffer from issues such as: running slow under heavy user load Inconsistency across different OS Poor usability  Performance testing can also be used as a diagnostic aid in locating communications bottlenecks

4. 4 Performance Testing (Process) Run Test Analyze Optimize

5. 5 Performance Testing(Objectives)  Application Response Time  Configuration Sizing  Reliability  Capacity Planning  Acceptance  Bottleneck Identification  Regression  Product Evaluation

6. 6 Types of performance testing  Load Testing  Stress Testing  Spike Testing  Endurance Testing  Volume Testing  Scalability Testing

7. 7 LOAD RUNNER INTRODUCTION :  Performance Testing Tool from Hewlett-Peckard (HP)  Examines System Behaviour And Performance while generating actual load  To test the application, LoadRunner emulates an environment where multiple users work concurrently  Supports large number of protocols  Version used for testing : LoadRunner 12.01

8. 8 LOAD RUNNER COMPONENTS OF LOAD RUNNER : 1. VuGen 2. Controller 3. Analysis

9. 9 Plan Load Tests PERFORMANCE TESTING PROCESS Create Vuser Scripts Create Load Scenarios Run Test Scenarios Analyze Results Monitor Test Scenarios

10. 10 Load Runner Architecture

11. 11 Load Runner Architecture: VUGen VUGen or Virtual User Generator is an IDE (Integrated Development Environment) or a coding editor. It is used to replicate System Under Load(SUL) behavior. It provides a “recording” feature which records communication to and from client and server in form of a coded script- Vuser script.

12. 12 Load Runner Architecture : Controller It is the main component which controls the load simulation. It controls all the users in a scenario from a single workstation. For example- how many Vusers to simulate against each business process or Vuser Group

13. 13 Load Runner Architecture : Analysis It reads the database file of errors and exceptions, which is result of execution of load scenario. It performs various types of analysis and generates graphs. The graphs show various trends to understand the reasoning behind errors and failure under load; thus help figuring whether optimization is required in SUL, server or infrastructure.

14. 14 Load Runner Architecture: Agents Machine Various machines where virtual users are spread. It is also called Load Generator or Load injector.

15. 15 Virtual User Generator (VuGen)  The purpose of VUGen is to create VUScripts that are used to simulate a real-like virtual-user  Also provides replay option for the scripts  Helps to incorporate scripts in LoadRunner scenario

16. 16 VuGen: Script Development Process Record the Script Enhance the Script Replay And Verify Configure Run Time Settings Use For Load Scenarios

17. 17 Features Related to VuGen  VUScripts  Actions : Set of user transactions performed in the System Under load to achieve a defined task  Transactions : Mechanics to measure server response time for any operation  Comments : To describe an activity, a piece of code or a line of code

18. 18 VuGen Parameterization What is Parameterization ? Replacing hard coded values in the script is called Parameterization. Parameterization helps in : > Reducing script size > allows you to test your script with different values > Avoiding cache effect Steps in Parametrization Replace the constant values in Vuser Script with parameters Set the data source for the parameter, so different values can be selected at run time

19. 19 VuGen Parameterization Date/Time – Whenever we have to replace a date value with a parameter, Date/Time parameter is used. Any post with past date is not valid. Group Name -We can generate a parameter on the basis of group that we select on controller for the script while execution. This parameter will only work while running the script on controller. File – Some time we want to pass the specific value in the script. In such cases, we use file and enter the values that want to use during execution. Random Number – As per need, Vugen also generates random value from the provided range. Vuser ID – When we run the script on controller, it assigns a unique id to each virtual user that emulate during the execution.

20. 20 VuGen Parameterization

21. 21 VuGen Parameterization

22. 22 VuGen Parameterization

23. 23 VuGen Parameterization

24. 24 WHAT IS CORRELATION ? Mechanism to define relationship between two variables or entities The method to handle the dynamic values created during the script execution Load Runner uses the dynamic data generated by the server instead of using the recorded values CORRELATION

25. 25 CORRELATION NEED OF CORRELATION : To prevent the script from failing during playback To capture dynamic values from steps To fetch the dynamic values generated by the server and use them to replay the script

26. 26 TYPES OF CORRELATION : 1. Automatic Correlation 2. Manual Correlation CORRELATION

27. 27 CORRELATION

28. 28 CORRELATION

29. 29 CORRELATION

30. 30 Checkpoints It compares stored value with actual i.e. present value and reports pass or fail status. It can be created during recording or while enhancing the Vuser script. Types - Text Checkpoint Image Checkpoint

31. 31 Checkpoints Text Checkpoint: It allows you to add a user-defined check that searches for a text string on a web page while running. Image Checkpoint: It allows you to add a user-defined check that searches for an image on a web page during the run.

32. 32 Checkpoints

33. 33 Checkpoints

34. 34 Checkpoints

35. 35 Rendezvous Point It is used to emulate heavy user loads on server. It instructs multiple Vusers to perform tasks at exactly the same time. It is inserted into the script to calculate the peak load of the server. It is put exactly before the transaction where we want Vusers to access system simultaneously.

36. 36 Controller (Rendezvous point)

37. 37 Rendezvous Point

38. 38 Service Level Agreement (SLA) It is a part of a service contract, where a service is formally defined. In this, particular aspects of the service- scope, quality, responsibilities are agreed between the service provider and the service user. It constitutes a measurable requirement that can be tested and marked as “pass” or “fail” accordingly. Example- Response time, System availability

39. 39 Run-Time settings It allows Vugen with different settings which works on script execution. It helps testers in many ways: - To emulate real user. - Allow to get detailed information for the virtual user. - Retrieve Performance status for the graph. - Automatic transaction Error handling

40. 40 Run Logic

41. 41 Pacing

42. 42 Think time

43. 43 Miscellaneous

44. 44 Controller  Load Runner Controller organizes and manages all the elements of a load test scenario  Runs V-user Groups  Controls the initialize, run, pause, and stop conditions of each V- user  Displays the status of each V-user  Displays any messages from V-users  Monitors system and network resources

45. 45 Scenarios in Controller  A scenario is a file that defines the V-users execution, the number of V-users to run, the goals of the test, the computer that hosts the V-users, and the conditions under which to run the Load Test.

46. 46 Types of Scenarios  Manual Scenario Manage your Load Test by specifying the number of Virtual users to run  Goal-Oriented Scenario Allow Load Runner Controller to create a Scenario based on the goals you specify

47. 47 Controller Controller (Design view)

48. 48 Controller (Run view)

49. 49 Controller (V-users)

50. 50 Controller (Ready State)

51. 51 Controller (Graph)

52. 52 Controller (Exporting Graph)

53. 53 Analyzer The aim of the analysis session is to find the failures in your system’s performance and then pinpoint the source of these failures. Load runner analysis provides: 1.Filtering 2.Regrouping 3.Legend filtering 4.Drill down 5. Duplicate graphing to separate data

54. 54 The Analyzer Window

55. 55 Explaining the Analyzer window : Session Explorer pane: In the upper left pane, Analysis shows the reports and graphs that are open for viewing. From here you can display new reports or graphs that do not appear when Analysis opens, or delete ones that you no longer want to view. Properties window pane: In the lower left pane, the Properties window displays the details of the graph or report you selected in the Session Explorer. Fields that appear in black are editable. Graph Viewing Area: In the upper right pane, Analysis displays the graphs. By default, the Summary Report is displayed in this area when you open a session. Graph Legend: In the lower right pane, you can view data from the selected graph.

56. 56 Analysis Graphs

57. 57 Connections per second graph

58. 58 Average Transaction Response Time Graph

59. 59 Running Vusers Graph Before Filtering

60. 60 Running Vusers Graph After Filtering

61. 61 Analyzer Merge Graph Two graphs maybe required to be merged to bring more meaningful information. Open the graph merge option, ensure you have at least one graph opened already, which has to be merge. The utility will assume we want to add another graph to the already opened graph. It overlay the content of two graphs that shares a common x-axis. Left Y-axis on the merged graph show’s the current graph’s value & Right Y- axis show the value of Y-axis of the graph that is merged.

62. 62 Merge Graph

63. 63 Merge Graph

64. 64 Merge Graph Here, we’re merging Throughput graph with Hits per Second graph.

65. 65 Crossing with Results Cross Scenario Analysis LoadRunner can superimpose the generated results onto a single cross- scenario graph. This process helps directly compare both results and generate cumulative report. If we’ve multiple scenario running already, we can use the results folder to cross match the statistics. Cross-scenario analysis is useful for: >benchmarking hardware > testing software versions > determining system capacity

66. 66 Cross Scenario Analysis

67. 67 Cross Scenario Analysis

68. 68 Cross Scenario Analysis

69. 69 Cross Scenario Analysis

70. 70 Cross Scenario Analysis

71. 71 Copyright © 2011 Tata Consultancy Services Limited THANK YOU !