In this video, Mike Smith introduces additional arguments to the command-line instruction to generate a results dashboard after the test has run.
- If I'm running a very simple load test…and the expectation is to report…on the amount of users that hit the website or server…and what kind of response codes came back,…I could run the test as I've already done in the CLI,…generate the .jtl file,…and then use that jtl file…to graph the results within JMeter.…I could ask JMeter to do most of that for me…by creating a dashboard after running the test.…To do this,…I'm going to add two very simple…switches to my command line instruction.…
- e will tell JMeter to perform any action following it…only after the test has completed and the -o,…followed by a name.…This will instruct JMeter to create this dashboard…in a folder of that name.…I'm going to call mine demoresults…and I'm also going to just rename my .jtl file…just to make sure there's no duplication errors…and then I'm going to hit return.…This allows the test to run and when this is finished,…I'm going to go and find that dashboard folder…and take a look at the results.…
My test has run and I'm ready to look at the results.…
- What is load testing and why do we do it?
- Creating and running load tests
- Improving a test by adding timers and assertions
- Running your load test through the CLI
- Saving CLI results to a .jtl file
- Importing a .jtl file to JMeter graphs
- Creating an HTML dashboard at CLI runtime