[ grinder-Feature Requests-2432898 ] Log test names early

SourceForge.net <[email protected]> Sat, 22 Oct 2011 16:55:16 -0700
Newsgroups gmane.comp.java.grinder.devel
Message-ID <[email protected]>
Feature Requests item #2432898, was opened at 2008-12-16 00:32
Message generated for change (Comment added) made by tbear
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=368598&aid=2432898&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: Open
Priority: 5
Private: No
Submitted By: Jarkko Sonninen (kasperx)
Assigned to: Philip Aston (philipa)
Summary: Log test names early

Initial Comment:
Currently the test names can be found in out file final statistics. If I have to abort a test run before it completes, the summary is not written. This is often the case in long stability tests. I use an analyzer to draw graphs from data files and knowing test names would clarify the report.
I suggest that test names are logged to a separate log file in a parseable format as soon as a test case introduces itself. 

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

Comment By: Travis Bear (tbear)
Date: 2011-10-22 16:55

Message:
+1

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

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

------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev