[ grinder-Bugs-2816501 ] Test numbers larger than 6 digits get truncated in out file

"SourceForge.net" <[email protected]>
Newsgroups gmane.comp.java.grinder.devel
Message-ID <[email protected]>
Bugs item #2816501, was opened at 2009-07-04 03:23
Message generated for change (Settings changed) made by philipa
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=2816501&group_id=18598

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core engine
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Vivin Paliath (vivin)
>Assigned to: Philip Aston (philipa)
Summary: Test numbers larger than 6 digits get truncated in out file

Initial Comment:
The details are available in this thread:

http://www.nabble.com/Unique-test-numbers-to24300372.html#a24312021

---

The problem seems to arise when there are more than 6 digits in the test number. Here's a snippet from the data file for Test number 1011000

3, 0, 1011000, 1246412433526, 148, 0, 0, 0, 0, 0, 0, 0

There are two entries for it, in the out file:

(Test 101100 1000         0            166.44       699.80       0.40         0.00         0.00         0            0.00         0.00         0.00)         "LoginTask(101) Log into the app"
(Test 101200 1000         0            163.43       163.64       0.40         0.00         0.00         0            0.00         0.00         0.00)         "LoginTask(101) Log into the app"
(Test 101300 1000         0            292.66       547.55       0.40         0.00         0.00         0            0.00         0.00         0.00)         "LoginTask(101) Log into the app"
(Test 101400 1000         0            859.44       671.39       0.40         0.00         0.00         0            0.00         0.00         0.00)         "LoginTask(101) Log into the app"
(Test 101500 1000         0            67.89        86.10        0.40         0.00         0.00         0            0.00         0.00         0.00)         "LoginTask(101) Log into the app"
(Test 101600 1000         0            1107.56      1256.31      0.40         0.00         0.00         0            0.00         0.00         0.00)         "LoginTask(101) Log into the app"
(Test 101700 1000         0            53.58        305.22       0.40         0.00         0.00         0            0.00         0.00         0.00)         "LoginTask(101) Log into the app"
(Test 101800 1000         0            39.24        273.68       0.40         0.00         0.00         0            0.00         0.00         0.00)         "LoginTask(101) Log into the app"
(Test 101900 1000         0            470.13       269.41       0.40         0.00         0.00         0            0.00         0.00         0.00)         "LoginTask(101) Log into the app"
...
...
(Test 101100 1000         0            216.25       634.93       0.40         0.00         0.00         0            0.00         0.00         0.00)         "LoginTask(101) Log into the app"

There should only be one, but two show up because one of the numbers is truncated.

There are 10 recorded pages for the LoginTask task. So it should list Test 101100, 101200. ... , 1011000. The last test is actually displayed but the last digit gets chopped off.

There is a quick fix right now (http://www.nabble.com/Unique-test-numbers-to24300372.html#a24312021) which is to change net.grinder.statistics.StatisticsTable.COLUMN_WIDTH. However, Grinder should automatically adjust the width based on the longest test number.

----------------------------------------------------------------------

>Comment By: Philip Aston (philipa)
Date: 2010-01-03 15:57

Message:
Fixed in svn:
http://grinder.svn.sourceforge.net/viewvc/grinder?view=rev&revision=4219

Will be in next release.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=2816501&group_id=18598

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.