|
|
|
|
|
|
71
|
> The Installing Java instructions should seek to minimize the number of steps and the number of concepts a new-to-the-track practitioner needs to learn to get to coding.
|
71
|
> The Installing Java instructions should seek to minimize the number of steps and the number of concepts a new-to-the-track practitioner needs to learn to get to coding.
|
|
72
|
|
72
|
|
|
73
|
References: [[1](https://github.com/exercism/java/issues/395#issue-215734887)]
|
73
|
References: [[1](https://github.com/exercism/java/issues/395#issue-215734887)]
|
|
|
|
74
|
+
|
|
|
|
75
|
+### Name test class after class under test
|
|
|
|
76
|
+
|
|
|
|
77
|
+> If you're testing a class called `SomeClassName` then your test class should be called `SomeClassNameTest`.
|
|
|
|
78
|
+
|
|
|
|
79
|
+> The exception to this is if the tests are split into several test classes where each test class tests different functionality. In that case each class should be named `SomeClassNameFunctionalityTest` where `Functionality` is the name of the functionality to be tested in that class. See the [clock exercise](https://github.com/exercism/java/tree/master/exercises/clock) as an example.
|
|
|
|
80
|
+
|
|
|
|
81
|
+References: [[1](https://github.com/exercism/java/issues/697)]
|