Bug 63878 - Improved execution output from command line
Summary: Improved execution output from command line
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: unspecified
Hardware: PC
: P2 enhancement (vote)
Target Milestone: JMETER_5.2
Assignee: JMeter issues mailing list
Depends on:
Reported: 2019-10-24 07:10 UTC by Ville
Modified: 2019-10-24 07:10 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Ville 2019-10-24 07:10:33 UTC
When Jmeter is executed from command line the below output is displayed

Creating summariser <summary>
Created the tree successfully using C:\Temp\Test.jmx
Starting the test @ Wed Oct 23 13:58:14 EEST 2019 (1571828294937)
Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445
summary =      0 in 00:00:00 = ******/s Avg:     0 Min: 9223372036854775807 Max: -9223372036854775808 Err:     0 (0.00%)
Tidying up ...    @ Wed Oct 23 14:20:34 EEST 2019 (1571829634151)
... end of run

Sometimes especially with scalability tests or heavy performance tests or tests with long duration the output should display more about where tests are going. For example if iterations are defined the Jmeter could display something like this:
1 iteration took 0:00:30 with 0.00% errors
2 iteration took 0:00:34 with 0.00% errors
3 iteration took 0:00:31 with 0.03% errors
...and so on. This would indicate that test execution is running and in what time/iteration the possible errors started to occur.

If duration is defined (for example tests are executed for 20 minutes or 1 hour or 4 hours) there could be a definition for output interval. Maybe 1 minute being the min value.
Tests executed for 0:10:00 with 0.00% errors
Tests executed for 0:20:00 with 0.00% errors

If I execute a test with 2 hours and all of my tests starts to fail after 20mins because of wrong configuration I would like to get this information as soon as possible. Also sometimes it happens that tests are jammed for any reason (not Jmeter related). With this kind of output I would be able to see this immediately and start investigation.