db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2514) convert lang/closed.java to junit
Date Wed, 28 May 2008 14:35:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600489#action_12600489
] 

John H. Embretsen commented on DERBY-2514:
------------------------------------------

Narayanan wrote:

> Also just as a matter of keeping to rules I am running all the tests. This step is unnecessary
I know. 

Actually, I think running "all" tests in most situations is a healthy practice. I have seen
several times in the past that some test is influenced (read: fails) as a side-effect of a
test running earlier in a larger test suite, such as suites.All. Examples are security policy
issues, cleanup problems, wrong assumptions in new test, etc. It would be good to catch such
issues prior to commit.

> convert lang/closed.java to junit
> ---------------------------------
>
>                 Key: DERBY-2514
>                 URL: https://issues.apache.org/jira/browse/DERBY-2514
>             Project: Derby
>          Issue Type: Test
>          Components: Newcomer, Test
>         Environment: convert lang/closed.java to junit
>            Reporter: Ramandeep Kaur
>            Assignee: Svein Erik Løvland
>            Priority: Minor
>         Attachments: Derby2514.diff, Derby2514_2.diff, Derby2514_3.diff
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message