In this video, Mike Smith highlights that the command-line interface for JMeter should be used when running your load tests.
- [Instructor] Running my load test is a simple process through JMeter's interface, but using this for anything other than test creation or debugging means that I'm using far more computer resources than I need to. Eventually, when I increase the load associated with the test, I'll start seeing errors, because there isn't enough RAM or CPU power for JMeter to use. Running a load test from the Command Line Interface, or CLI, can help alleviate that by using significantly less resources.
Running load tests within the Command Line also allows for distributive load testing, which is an advanced way of sending your load test file to multiple instances of JMeter to increase that load exponentially. The application openly recommends using the Command Line to do this. It's faster, more reliable, and the CLI can still save all of the results of information to a file for later examination. The CLI is the purest way of running a load test. If you'll be working with JMeter in the future, it's something you should become very comfortable with.
- 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