example: class1#m1 class2 will only run m1 from class1 (or none if m1 does not exist) will also run all methods from class2
NAME_ASCENDING in case the hash codes are equal. no more private compare method
…hod.toString used as a tiebreaker
In MethodSorterTest, I took into account the fact that the getDeclaredMethods method from Class returns methods in an arbitrary order. We can therefore expect 2 possible outcomes for the output of declaredMethods. I adapted the test to this reality.
Conflicts: src/test/java/org/junit/tests/AllTests.java src/test/java/org/junit/tests/experimental/rules/ExpectedExceptionRuleTest.java Merged changes from the HEAD branch Besides the merged changes also the approach to test for the failure has been changed to comply to the new way of testing in ExpectedExceptionTest. That no longer required the changes in ResultMatchers (with their accompanying tests)
…) and fixed the oddly indented brace