<< Back to previous view |
![]() |
[QB-2138] Jmeter Plugin didn't support decimal numbers
|
|
Status: | Closed |
Project: | QuickBuild |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | Priority: | Major |
Reporter: | hela cherif | Assigned To: | Steve Luo |
Resolution: | Won't Fix | Votes: | 0 |
Remaining Estimate: | Unknown | Time Spent: | Unknown |
Original Estimate: | Unknown | ||
Environment: | LINUXRH5 |
Description |
Hello,
The Jmeter plugin didn't support decimal numbers like 0.02 seconds in the fields : totalTime, averageTime ,minTime and maxTime. Please note that for performance Report , we usually work with the microseconds and not with seconds. So i need to have Jmeter Report with microsecondes unity which supports decimal numbers. Thanks Hela |
Comments |
Comment by Steve Luo [ 24/Jul/14 03:01 AM ] |
QuickBuild parses JMeter XML report and from the JMeter specification (http://jmeter.apache.org/usermanual/listeners.html#attributes), elapsed time is with the milliseconds, not microseconds or seconds.
So could you please tell me how you generate your JMeter XML reports and it would be better to attach your original XML reports here or send them to me (steve at pmease). |
Comment by hela cherif [ 20/Aug/14 03:29 PM ] |
Hello
This is an example of JMeter XML : <testresults version="1.2"> <sample ts="1408497595815" t="238" lb="OutboundNew" s="true" by="531"/> <sample ts="1408497595815" t="273" lb="InboundNew" s="true" by="229"/> <sample ts="1408497595816" t="281" lb="OutboundModif" s="true" by="680"/> <sample ts="1408497595816" t="257" lb="InboundModif" s="true" by="229"/> <sample ts="1408497595816" t="236" lb="Execution" s="true" by="229"/> </testresults> In the JMeter Specification, the time 't' is in milliseconds. In our case, this 't' is in microsecondes. So, we want that the JMeter Plugin supports the fractional time as t=0.238 milliseconds which equal to 238 microseconds, because now the JMeter Plugin converts 0.238 milliseconds automatically to 0 microseconds . else you support the micoseconds unity. Thanks Hela |
Comment by Steve Luo [ 21/Aug/14 03:00 AM ] |
Hi Hela,
In QuickBuild, we use millisecond as duration/period unit, and use Long to store the value, and this is compatible with most of the reports. It will impact a lot in order to support microsecond. So, I don't think we can support this in the near feature. Sorry. |