* Issue #253: Tried to improve grade school structure. Removed .db() function, added numberOfStudents functions and renamed the sort function to studentsByGradeAlphabetical. Added test to check that grade() gets the students in the order they were inserted. Removed getsStudentsInAGrade() test as what it was testing was already being covered by the tests before it.

* Added tests for protection agains mutation of the list object

* Issue #253: Make the sort test more generic. This to allow a broader range of implementations. Currently users are hindered into return the type HashMap<Integer, List<String>. This test update will check the order of any Map that maps to any Collection value type. This opens the doors for more possible types of solutions.

* dibs: I will implement exercise Clock

* Implemented clock exercise

* Issue #253: Tried to improve grade school structure. Removed .db() function, added numberOfStudents functions and renamed the sort function to studentsByGradeAlphabetical. Added test to check that grade() gets the students in the order they were inserted. Removed getsStudentsInAGrade() test as what it was testing was already being covered by the tests before it.

* Added tests for protection agains mutation of the list object

rectangles: polish example implementation

luhn: update tests and sample implementation

Phone number exceptions

Use an @Rule instead of @Test(expected=…)

Fixes #252. Passing invalid input to the constructor should now expect
an IllegalArgumentException.

Fixes #245.

Tracking issue: https://github.com/exercism/x-common/issues/491

dibs: I will implement exercise Matrix

rectangles: add to track

Meetup tests   assert reorder

Fixes #250.

Make root gradle project aware of binary-search again

Reorder queen-attack tests

Moved the ExpectedException declaration back to the top, where it was
before.

Fixes issue #241.

Issue #167: Refactored WordCountTest to have a setup method

twelve-days: add to track

Invoke JUnit assertEquals with Argument Order (expected, actual)

The JUnit API documents assertEquals as taking the expected argument
before the actual argument.  Failure to adhere to this can result in
very confusing test failure messages.

For example in testTransformOneValue 'old' contains 'A' and 'expected'
contains 'a'.  If the implementer does not lower-case the key, the
failure message is as follows if the argument order is
(actual, expected):

EtlTest > testTransformOneValue FAILED
    java.lang.AssertionError: expected:<{A=1}> but was:<{a=1}>
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.failNotEquals(Assert.java:834)
        at org.junit.Assert.assertEquals(Assert.java:118)
        at org.junit.Assert.assertEquals(Assert.java:144)
        at EtlTest.testTransformOneValue(EtlTest.java:27)

This is very confusing as "was:<{a=1}>" is exactly what we were hoping
the result would be.

sublist: add to track

* Issue #152: Made simple-cipher more approachable by splitting test classes in a more sensible way and making clear which steps they relate to.

* Changed SimpleCipherTest to use the junit Rule annotation for expected exceptions. Changed variable names in SimpleCipherTest to be more descriptive and moved the test cipherThrowsWithEmptyKey from step three to step two.

* Added HINT.md which explains how to run only one test class.

* Changed HINT.md in simple-cipher to refer to the actual test file names and not to contain the same information as in SETUP.md