Software engineering can be described as the orchestration of a quasi-denumerable set of moving parts.
With so many moving parts, breakages occur. One main goal as a “software craftsperson” is to never expose customers to the affects of these breakages. Test-driven development rose from this desire. Accepting that systems break, even in production, motivated loosely coupled and shared-nothing system architectures.
Spring has had a really nice unit test framework available for a while now, but the documentation can be a bit daunting. Here’s a super-simple example of adding dependency injection to an integration test:
The Galileo version of Eclipse doesn’t ship with a default keybinding for creating a unit test for the current class, but you can add one easily enough. Navigate to Preferences > General > Keys, and search for “junit test case”:
Click the “Binding” field, hit the keystroke (I used shift-control-option-command-t), and click Apply.
I haven’t found a way to jump to the referring test for a given class, though. IDEA’s JUnit plugin had that and I miss it. :-\