You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2006/11/01 16:36:21 UTC
[jira] Resolved: (DERBY-1971) Make TestConfiguration set
descriptive names for TestSuite objects it instantiates
[ http://issues.apache.org/jira/browse/DERBY-1971?page=all ]
Kristian Waagan resolved DERBY-1971.
------------------------------------
Fix Version/s: 10.3.0.0
Resolution: Fixed
Assignee: Daniel John Debrunner
I think this has been fixed by Dan as part of another issue, so I'm setting this to fixed.
Will close the issue soon if nothing pops up.
> Make TestConfiguration set descriptive names for TestSuite objects it instantiates
> ----------------------------------------------------------------------------------
>
> Key: DERBY-1971
> URL: http://issues.apache.org/jira/browse/DERBY-1971
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Kristian Waagan
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> Several JUnit tools make use of TestSuite.getName() to display test hierarchies and other information. An example is junit.swingui.TestRunner.
> Currently, the TestSuite objects generated by TestConfiguration are not given names.
> To improve readability and the level of information, descriptive named should be set. At a minimum, the associated framework should be indicated. Another point is whether the user set name (if any) of the "root test suite" should be propagated or not.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira