This document provides an introduction to functional, performance, and non-functional testing with JMeter. It discusses what JMeter is, how it works, its main components, and how to perform tests. It also provides demonstrations of creating functional and performance tests with JMeter.

1. Introduction to Jakarta Jmeter With Philip Bannon

2. Mail: [email_address] ewbay.com

3. Presentation Objectives Give you an introduction into: Functional testing with Jmeter

4. Performance testing with Jmeter

5. Non-Functional testing with Jmeter Help you figure out if Jmeter is suited for testing your applications

6. Brief Introduction to Jmeter So what is Jmeter: Jmeter is an automated testing tool from the Jakarta project (active)

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)

10. What can You do with it?? Most test related activities: Perform automated Functional Tests

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

12. Carry out Non-Functional Tests

13. Unit Testing

14. Benifits of Using Jmeter Excellent cost saving solution for small projects as it is an open source tool

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

21. Build Blocks Test Plan

22. Thread Group

23. Controllers & Config elemets

24. Samplers

25. Listeners

26. Timers

27. Assertions

28. Pre-Processor Elements

29. Post Processor Elements

30. Thread Group Thread Group elements are the beginning points of your test plan. All samplers and controllers are children of a thread group node.

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

32. We can also control the following via the thread Group: Set the number of Threads

33. Set the Ramp Up Time

34. Set the number of test itterations

35. Controllers & Config Elements Logic Controllers: Logic Controllers let you control the flow of your test for example you can have IF conditions for selecting certain samplers. Configuration Elements: Config elements can be used to set up defaults and variables for later use by samplers. HTTP Manager

36. HTTP Request Defaults

37. Cache Managers

38. Cookie Manager

39. Logic Controllers Logic Controllers let you control the flow of your test.

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

41. Some Examples: ForEach Controller

42. While Controller

43. Loop Controller

44. IF Controller

45. Run Time Controller

46. Interleave Controller

47. Throughput Controller

48. Run Once Controller

49. Samplers Samplers tell Jmeter to send requests to a server. For example, you can add a HTTP Request sampler if you need to perform a POST, GET, DELETE on a HTTP service

50. Some usefull samplers: HTTP Request

51. FTP Request

52. JDBC Request

53. Java Request

54. SOAP/XML Request

55. RPC Requests

56. Listeners Listeners provide access to the information that Jmeter gathers about the tests which are executing. For instance Response codes, messages etc. Some Listeners are: View Results Tree: This shows the details of the sampler requests and the responses and can display them in different formats Summary Report: This shows a summary in tabular form of the results from executing samplers Graph Results: This will show us the response times and response codes on a graph Listeners can write their information out to files in XML or CSV format

57. Timers By default, a Jmeter thread will send send requests without pausing between each sampler. This may not be what you want....

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!

61. Assertions A test isn't a test unles it checks something!

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

65. Pre-Processor & Post Processor A Pre-Procesor is something that will happen before a sampler executes.

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

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

68. For exmple: Perfoming Xpath Extractions

69. Regular Expression Extractions

70. Lets do a functional Test DEMO!!

71. Record and playback Jmeter can act as a proxy server between your browser and the web recording your actions.

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

73. Lets do another small demo?

74. Performance Testing Good Performance testing

75. What is performance testing Performance Testing sets the ‘best possible’ performance expectation under a given configuration of infrastructure. It also highlights early in the testing process if changes need to be made before application goes into production

76. Aims of Performance Tests What level of load can your Application handle

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

81. Some definitions Load Testing Load testing identifies the maximum operating capacity of your app as well as any bottlenecks Stress Testing Stress testing is focused on finding out the robustness and availability of your app under heavy loads (When will your system fail?) Soak Test Like load but over a long duration Scalabitilty testing This will determine whether adding extra hardware will increase your apps response time

82. Performance Testing The Usual Problem Write Code

83. Execute Unit Tests

84. Pass it to QA

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

86. A Better Way Performance test artifacts as soon as they pass Unit and Functional Testing

87. Fast feedback for Dev's

88. No Suprises

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

90. What do you need for Performance Testing System Under Test i.e. Your application!

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!

98. Traffic Model, Traffic Model, Traffic Model! Without a Traffic Model you just putting load on your server for the sake of it!

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!

101. Demo Lets write a basic script in Jmeter to test performance of a HTTP web app

102. Non-Functional Testing with Jmeter Demo

103. Automated Testing Jmeter integrates seemlessly with CL tools ANT

104. HTML Report Generation

105. Q&A Questions and hopefully answers