jMeter

Test Your Performance To Its Limits And Beyond With JMeter: How-To

JMeter, what-now?

What is JMeter? A tool used for load as well as performance testing and analysis. Jeneraly the app is providing you with numbers you will use to understand how the application under test is doing. The data JMeter will be generating is great for benchmarking performance in various different environments, gains after tuning measurements as well as basic load testing.

JMeter produced data is of better use if compared to a vastly different set of results (meaning every set of results is representing a different set of various conditions). The data received from JMeter will also differ in any project due different requirements, query complexity, software versions and many more factors.

Configuring JM

When all is configured and JM proxy is at place one may simply visit a website he wishes to test and by clicking on different buttons, etc. All the appropriate data will be added as entries to your JM test plan. But for all to work JMeter has to be configured in an appropriate way.

Thread Group creation

  • Start JM
  • There will be a tree in the top where you may and should choose ‘Test Plan’
  • Right click it and you will have the potential of: add, then threads, then thread group
  • Afterwards select the created group (and you will have the power of defining the number of treads that will be replacing concurrent users that will be going while the test plan’s being executed)
  • Right-click on the group, afterwards choose add, then configure element, then HTTP request defaults
  • Fill in the IP or the server name (warning: JMeter is not friends with local hosts and localhost environments for undefined reasons thus, if it’s your case, things may get tricky)
  • Fill in the Port Number (8080 is what default JRS installations show)
  • If necessary, you may configure yourself a proxy server in the boxes on the bottom

JMeter Proxy Configurations

  • Select workbench and right-click it
  • Select add, then non-test elements, then HTTP Proxy Server
  • Modify values
    • Port: change it from default 8080 to something that is not used
  • Then go ‘Patterns to include’ click on the ‘add’ button. Add a pattern fit in your case
  • Hit the ‘Start’ button

Next steps

  • Configure browsers for them to go through proxy
  • Create your test plan via a browser
  • Turn JM’s reporting feature on
    • Select Thread group in JM and right-click it
    • Add, then listener, then aggregate report
    • While thread group is still selected you are to choose a number of threads, the same threads that will be representing concurrent users

All that is left to do is running the test plan of course, analyzing the logs an continue with your website testing. The best of luck to you!


TestFort Blog

About TestFort Blog

TestFort blog is an official blog of TestFort QA Lab company and is dedicated to various QA and software testing issues.


no comments yet

Be the first to comment this post!

Would you like to share your thoughts?

Software testing & QA blog by TestFort © 2017

×