Harmony
  1. Harmony
  2. HARMONY-1960

[classlib] Tool to help spot potential junit usage issues

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Classlib
    • Labels:
      None

      Description

      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.

      1. check-junit-code
        10 kB
        Mark Hindess

        Issue Links

          Activity

          Mark Hindess created issue -
          Mark Hindess made changes -
          Field Original Value New Value
          Attachment check-junit-code [ 12343610 ]
          Alexei Zakharov made changes -
          Link This issue is related to HARMONY-1976 [ HARMONY-1976 ]
          Mark Hindess made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Assignee Mark Hindess [ hindessm ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Mark Hindess
              Reporter:
              Mark Hindess
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development