harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess (JIRA)" <j...@apache.org>
Subject [jira] Closed: (HARMONY-1960) [classlib] Tool to help spot potential junit usage issues
Date Fri, 03 Aug 2007 07:56:53 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mark Hindess closed HARMONY-1960.

    Resolution: Fixed
      Assignee: Mark Hindess


> [classlib] Tool to help spot potential junit usage issues
> ---------------------------------------------------------
>                 Key: HARMONY-1960
>                 URL: https://issues.apache.org/jira/browse/HARMONY-1960
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>            Reporter: Mark Hindess
>            Assignee: Mark Hindess
>            Priority: Trivial
>         Attachments: check-junit-code
> I've written a simple tool to help identify potential junit test issues - such as arguments
to assertEquals being in the wrong order which can lead to confusing errors and bug reports.
 I figured I'd attach it to a JIRA so that people can look at it and maybe improve some of
our unit tests.  Suggestions for improvements would be very welcome.  It requires Perl and
probably works best on unix.
> It finds over 5000 potential issues with our tests so I don't plan to fix them all myself.
 It would be nice if we could at least try to ensure that everyone understands the issues
and adopts best-practice to avoid creating any more potential problems.

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

View raw message