db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-2028) Make sure JUnit tests name their suites
Date Mon, 06 Nov 2006 15:48:41 GMT
     [ http://issues.apache.org/jira/browse/DERBY-2028?page=all ]

Kristian Waagan closed DERBY-2028.
----------------------------------

    Fix Version/s: 10.3.0.0
       Resolution: Fixed

All existing suites running as part of 'suites.All' are now named.
If new, unnamed suites are introduced, they should be handled as separate Jira issues.

> Make sure JUnit tests name their suites
> ---------------------------------------
>
>                 Key: DERBY-2028
>                 URL: http://issues.apache.org/jira/browse/DERBY-2028
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>            Priority: Trivial
>             Fix For: 10.3.0.0
>
>         Attachments: derby-2028-1a.diff, derby-2028-1a.stat
>
>
> To make the information displayed by various JUnit tools more useful/descriptive, all
test suites should be named.

-- 
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

        

Mime
View raw message