In this example we will add a thread group to the test plan from the submenu item “Threads (users)”. Right clicking on the Test Plan item in the pane on the left then hovering over the add sub-item opens up an options menu showing all the items you can add to the test plan. One of the advantages of the JMeter UI is great discoverability of all the different options for testing. This is the top level component of a JMeter test, and is largely a container for other components with some configuration options which we won’t touch for this simple load test. It will look something like this:Ĭreated for you and displaying in the pane on the left-hand side is a test plan. JMeter UIĪfter downloading JMeter (I’m using v5.4.1 for this post) and adding it your PATH environment variable, the JMeter UI can be opened from the command line by running the command jmeter. I recommend opening the images in a separate tab (right click and select “Open image in new tab”) in order to see the detail. These capture the whole screen, but therefore make the detail hard to see when embedded in the blog. I have provided images to alongside the instructions. In this article, I will demonstrate how to perform a simple load test hitting an HTTP endpoint with lots of requests concurrently to simulate a large user base all using the service at the same time. Load testing means putting an application under load by making it do lots of work, for example making lots of requests to it. It was originally designed for testing Web Applications but has since expanded to other test functions”. As described on their website “The Apache JMeter™ application is open source software, a 100% pure Java application designed to load test functional behavior and measure performance.
0 Comments
Leave a Reply. |