You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Mark Hindess (JIRA)" <ji...@apache.org> on 2006/10/25 12:43:17 UTC
[jira] Updated: (HARMONY-1960) [classlib] Tool to help spot
potential junit usage issues
[ http://issues.apache.org/jira/browse/HARMONY-1960?page=all ]
Mark Hindess updated HARMONY-1960:
----------------------------------
Attachment: check-junit-code
> [classlib] Tool to help spot potential junit usage issues
> ---------------------------------------------------------
>
> Key: HARMONY-1960
> URL: http://issues.apache.org/jira/browse/HARMONY-1960
> Project: Harmony
> Issue Type: Improvement
> Components: Classlib
> Reporter: 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.
-
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