AtUnit minimizes boilerplate code in unit tests and guides test development by enforcing good practices.
- mark exactly one field with
@Unitto indicate the object under test. - mark fields with
@Mockor@Stubto obtain mock objects - inject your tests, and your test subjects, using your favorite IoC container
AtUnit integrates with JMock or EasyMock to provide mock objects:
- obtain a JMock context simply by declaring a field
- annotate fields with
@Mockto obtain JMock or !EasyMock mock objects - annotate fields with
@Stubto obtain a JMock or !EasyMock stub object
... or you can use your own mock objects plug-in with two easy steps:
- implement the
MockFrameworkinterface - annotate your tests with
@MockFrameworkClass(MyMockFramework.class)
AtUnit integrates with Guice or Spring to take all of the work out of dependency-injected tests.
With Guice:
- never see the
Injector, never write bootstrapping boilerplate! @Injecttest class fields without even defining aModule- declaratively obtain mock objects with
@Inject @Mock - if you need more binding flexibility, simply have your test class implement
Module
With Spring:
- annotate fields with
@Beanto get them from the Spring context - fields annotated with
@Beanwhich do not appear in your Spring context are added to it automatically! (This includes@Mockand@Stubfields.) - !AtUnit looks for a Spring XML file with the same name as your test, or you can specify the location yourself with
@Context("filename") - Most of the time, you don't even need a Spring XML file!
You can easily plug in other containers in two steps:
* implement the Container interface
* annotate your tests with @ContainerClass(MyContainer.class)
These Example AtUnit Tests are the quickest way to get started with AtUnit. They demonstrate most permutations of supported containers and mock frameworks, and illustrate the various ways AtUnit makes writing tests easier.