The end result can be the following:
public void receiveCommands(String commands) {
for (char command : commands.toCharArray()) {
switch(command) {
case 'f':
moveForward();
break;
case 'b':
moveBackward();
break;
case 'l':
turnLeft();
break;
case 'r':
turnRight();
break;
}
}
}
If you tried to write specifications and the implementation by yourself and if you followed the simplicity rule, you probably had to refactor your code a couple of times in order to get to the final solution. Simplicity is the key and refactoring is often a welcome necessity. When refactoring, remember that all specifications must be passing all the time.
Refactor only after all the tests have passed.
Benefits: refactoring is safe.
If all the implementation code that can be affected has tests and if they are all passing, it is relatively safe to refactor. In most cases, there is no need for new tests; small modifications to existing tests should be enough. The expected outcome of refactoring is to have all the tests passing both before and after the code is modified.
Benefits: refactoring is safe.
If all the implementation code that can be affected has tests and if they are all passing, it is relatively safe to refactor. In most cases, there is no need for new tests; small modifications to existing tests should be enough. The expected outcome of refactoring is to have all the tests passing both before and after the code is modified.
The full source for this requirement can be found in the req04-commands branch of the tdd-java-ch04-ship repository (https://bitbucket.org/vfarcic/tdd-java-ch04-ship/branch/req04-commands).