Skip to main content

JMeter: Creating First Load Test

What we want to do
  1. Simulate concurrent users
  2. Simulate requests
  3. Generate reports
  4. Troubleshooting

JMeter GUI
Test Pan Plan is a root element where all test related settings are define.
In Thread Group we can define pool of user to simulate load on the test
Work Bench is for non test helpers
 image

Common terms in JMeter
  • User           ⇒ Thread
  • Request     ⇒ Sampler
  • Report       ⇒ Listeners

Setting up the load test

1. Simulate concurrent users

  • Add thread > Thread Group
    • Number of Threads - concurrent users =10
    • Ramp-Up Period - seconds until all users are active =1 (eg. if user define 10 Threads and 100 Ramp-Up Period then, it means each thread will start in 100/10=10 seconds time difference)
    • Loop Count - how many repetitions =1
    • Calculating think time

                                     Ramp-up time                 = 120 seconds
                                     Number of users             =  30
                                     Then think time will be  =  ramp up time/number of users
                                                                            = 120/30 = 4 seconds


image

    2. Simulate requests

      • Add Sampler > HTTP Request
      • image

    3. Generate reports

    • Add > Listener > Aggregate Graph
    • Add > Listener > View Results Tree

    Running the load test
    • Click on Run > Start or "ctr+r"
    • Click on "Aggregate Graph"
      • Click "Display Graph" for chart

     

    image

     

    • Click on "View Results Tree"

     

     

    image

     

    • To Re-run the test
      • Click on Run > Clear All or "ctr+e"
      • Click on Run > Start or "ctr+r"

    Troubleshooting
    View Results Tree hold the "Request" and "Response" data for each request so it's a really good place to verify, if test is running correctly or not.
    "Request" Tab shows data sent to web server
    "Response Data" Tab shows server response body
     
     
     

    Comments

    Popular posts from this blog

    ERROR: Ignored call to 'alert()'. The document is sandboxed, and the 'allow-modals' keyword is not set.

    Recently I found this issue while writing code snippet in "JSFiddle". And after searching, found this was happening because of new feature added in "Chrome 46+". But at the same time Chrome doesn't have support for "allow-modals" property in "sandbox" attribute. Chromium issue for above behavior: https://codereview.chromium.org/1126253007 To make it work you have to add "allow-scripts allow-modals" in "sandbox" attribute, and use "window.alert" instead of "alert". <!-- Sandbox frame will execute javascript and show modal dialogs --> <iframe sandbox="allow-scripts allow-modals" src="iframe.html"> </iframe> Feature added: Block modal dialog inside a sandboxed iframe. Link: https://www.chromestatus.com/feature/4747009953103872 Feature working Demo page: https://googlechrome.github.io/samples/block-modal-dialogs-sandboxed-iframe/index.html

    Application Design Notes

    Don’t be afraid to write your own code, but be absolutely sure you need to Don't reinvent the wheel Learn more about your libraries and take full advantage  Date time calculation is hard ( leap second ,  leap year ), use trusted library  js-joda ,  momentJs ,  joda (java) Simple is better than perfect (nearly) every time If you can deliver a sub-optimal solution (that solves the problem but has known limitation) in a week instead of a full featured one in a month DO, IT Simple system are Easy to reason about  Easy to debug Easy to refactor Easy to learn Simple doesn't mean you skip good engineering, but you can use duct tape. Build things the right way from the start, refactoring is hard and expensive Security Manage and store passwords securely Telemetry Common retrofitting "grunt work" Internationalization + localization Web Content Accessibility Factoring and styling HTML UI Adding unit test to an existing codebase LOG LOG LOG Log, but do it right We spend lot of t

    How to store user password at server!!!

    Trick is, you should never store user password… never ever. Now the real question is, then how to authenticate and authorize the user with password. And answer is when user enter the password, we should encrypt the password and store the hints. So next time when user enter the password we follow the same process and compare hints, if both hints are same then password is matched, else it is wrong password. Next question will be, what kind of hints, and how to generate these hints. In simple term hints are the obfuscated and fragmented form of user password. And very important part is hints generation process, which have to be collision resistant , means there will be very less possibility to find the data which generate same hints (like Cryptographic hashing functions ). Below is the simple checklist of password hashing and storing, which you should always keep in mind. PS You're Probably Storing Passwords Incorrectly Storing Passwords - done rig