Unit Testing

Unit testing helps ensure the quality of the software developed by eobjects.org. A unit test is a piece of code (test code) that verifies the behaviour of a unit of production code. We encourage this type of development very much since a unit test has a lot of positive effects on the code:

• You verify the behaviour of your code.
• The test serves as documentation for the production code and a good way to learn about the behaviour of the system.
• The impact of a change in existing code will result in failing tests, if the change has negative effects.
• Requirements can be specified as a unit test without having to do the implementation up front.

Continous Integration

We have a continous integration system, Hudson which serves as a central execution mechanism of unittests and thereby as a way to report the status of our systems. You can visit the Hudson system at:  http://eobjects.org/hudson/

See also

• JUnit:  http://www.junit.org/
• EasyMock:  http://www.easymock.org/
• The wikipedia article on unit testing:  http://en.wikipedia.org/wiki/UnitTesting