2. Mail: [email_address] ewbay.com

4. Performance testing with Jmeter

7. It's 100% Open Source

8. Written in Java so its completly portable

9. Can be used for Unit Test Tool for JDBC, FTP, LDAP, Web Services, JMS, HTTP and TCP connections (plus more)

11. Perform Performance tests ( Load, Stress, Soak)

12. Carry out Non-Functional Tests

13. Unit Testing

15. Robust in handling complex test scenarios that demand ‘n’ number of virtual users.

16. Complete portability and supports 100% all the Java based applications.

17. Less scripting efforts as compared to other tools because of its user effective GUI.

18. Really Designed to conduct Load, Stress, Volume & Endurance tests on the Web & Webservice based applications

19. HTTP & HTTPS load testing can be done without any adding additional pluggable samplers

20. How Jmeter works Jmeter simulates a group of users sending requests to a target server, and return statisticts that show the perfomance / funcationality of the target server / application via tables, graphs etc. Start Creates requests to target server and simulates a number of users End Jmeter gathers Data to calculate Statistical info Server Responds Jmeter Saves All Responses Report

22. Thread Group

23. Controllers & Config elemets

24. Samplers

25. Listeners

26. Timers

27. Assertions

28. Pre-Processor Elements

29. Post Processor Elements

31. As the name suggests, the thread group elements controls the number of threads Jmeter will use during the test.

33. Set the Ramp Up Time

34. Set the number of test itterations

36. HTTP Request Defaults

37. Cache Managers

38. Cookie Manager

40. Logic Controllers can change the order of request coming from any of their child elements

42. While Controller

43. Loop Controller

44. IF Controller

45. Run Time Controller

46. Interleave Controller

47. Throughput Controller

48. Run Once Controller

51. FTP Request

52. JDBC Request

53. Java Request

54. SOAP/XML Request

55. RPC Requests

58. We can add a timer element which will allow us to define a period to wait between each request.

59. Timers can act as a throttle!

60. Note the scope of the Timer!

62. Assertions are what do the checking

63. Assertions allow you to assert facts about the responses received from the application under test. Using assertions you can prove that your application is returning the correct data.

64. Jmeter will highlight when an assertion fails

66. A Post Processor executes after a sampler finishes its execution.

67. The are usufull processing the response which is recieved from the application

69. Regular Expression Extractions

72. This can help in writing your web tests.....

73. Lets do another small demo?

77. How fast your system will perform

78. Find bottlenecks

79. Determine how much hardware you'll need for Production (scalability)

80. How reliable is your software

83. Execute Unit Tests

84. Pass it to QA

85. Just before Production do some Performance testing....and Panic!!

87. Fast feedback for Dev's

88. No Suprises

89. Get the software out the door on time!!!

91. Benchmark & Profile

92. Realistic Hardware of what is or will be in production

93. Load Generating machines (Jmeter)

94. Monitoring tools

95. Data Repository

96. Prepare your environment (Network, storage etc)

97. Isolation!

99. Based on projections you should be able to work out what your users will be doing and how often!

100. This can all be reflected in your test!

104. HTML Report Generation