JMeter Tutorials | 13 | Why and how to run Jmeter in non-GUI mode | Fetch results in CSV file

When you start the JMeter instance, you can see in the command prompt, for actual load testing, use Jmeter in the CLI mode. Because when we perform heavy load testing, CLI is the best option to go for.
Why do we need to go for CLI (command line interface)?
1) Even if you are not at all going to use this, for interview sake you have to learn it.
2) The real reason is, it can be easily integrated with CI/CD tools like Jenkins, Bamboo etc.
3) The other important reason is, the fancy reports that we included in the listeners, will definitely consume a lot of CPU and memory, and as a result, the machine which was dedicated to testing the performance of other applications will perform poorly.
So How to execute JMeter tests via CLI?
1) Create a sample HTTP request test and save that as CLI_Test.jmx
2) Then execute the below command:
jmeter -n -t (location of your jmeter test script) -l (location of the result file)
Learn My other courses:
1)Selenium basics: bit.ly/2XtOt1F
2)Selenium Advanced: bit.ly/2WYieZe
3)TestNG Absolute Beginner Guide: bit.ly/2N6xgaM
4)Data-driven framework: bit.ly/2WVjSFT
5)Page Object Model: bit.ly/2IAXJZR
6)How to write XPath on our own: bit.ly/2KwMLql
7)Must know Java concepts for Selenium: bit.ly/31Ro7G8
8)Selenium Interview Questions: bit.ly/2N6xu1F
9)Java for Selenium Automation: bit.ly/2IylOAh
10)Maven beginner guide: bit.ly/2Rsigm0
11)Github Absolute beginner Guide: bit.ly/2Kxdzqj
12)REST Web services beginner guide: bit.ly/2N69rQq
13)Cucumber absolute beginner guide: bit.ly/2X0lSBB
14)Acceptance Testing (Fitnesse) beginner guide: bit.ly/2Y6oE55
15)Jenkins beginner guide: bit.ly/2X39fGb
Follow me on Instagram: bit.ly/2Ez36rH
Facebook: bit.ly/2TqPlis
#PerformanceTesting #JMeter #LAO #Tamil