|
|
@@ -11,34 +11,6 @@ When X is a name or "you".
|
|
11
|
11
|
If the given name is "Alice", the result should be "One for Alice, one for me."
|
|
12
|
12
|
If no name is given, the result should be "One for you, one for me."
|
|
13
|
13
|
|
|
14
|
|
-## Test-Driven Development
|
|
15
|
|
-
|
|
16
|
|
-As programmers mature, they eventually want to test their code.
|
|
17
|
|
-
|
|
18
|
|
-Here at Exercism we simulate [Test-Driven
|
|
19
|
|
-Development](http://en.wikipedia.org/wiki/Test-driven_development) (TDD), where
|
|
20
|
|
-you write your tests before writing any functionality. The simulation comes in
|
|
21
|
|
-the form of a pre-written test suite, which will signal that you have solved
|
|
22
|
|
-the problem.
|
|
23
|
|
-
|
|
24
|
|
-It will also provide you with a safety net to explore other solutions without
|
|
25
|
|
-breaking the functionality.
|
|
26
|
|
-
|
|
27
|
|
-### A typical TDD workflow on Exercism:
|
|
28
|
|
-
|
|
29
|
|
-1. Run the test file and pick one test that's failing.
|
|
30
|
|
-2. Write some code to fix the test you picked.
|
|
31
|
|
-3. Re-run the tests to confirm the test is now passing.
|
|
32
|
|
-4. Repeat from step 1.
|
|
33
|
|
-5. Submit your solution (`exercism submit /path/to/file`)
|
|
34
|
|
-
|
|
35
|
|
-## Instructions
|
|
36
|
|
-
|
|
37
|
|
-Submissions are encouraged to be general, within reason. Having said that, it's
|
|
38
|
|
-also important not to over-engineer a solution.
|
|
39
|
|
-
|
|
40
|
|
-It's important to remember that the goal is to make code as expressive and
|
|
41
|
|
-readable as we can.
|
|
42
|
14
|
|
|
43
|
15
|
# Java Tips
|
|
44
|
16
|
|