BibSonomy ::  tag ::

order by ( date | folkrank )

AtUnit minimizes boilerplate code in unit tests and guides test development by enforcing good practices. * mark exactly one field with @Unit to indicate the object under test. * mark fields with @Mock or @Stub to obtain mock objects * inject your tests, and your test subjects, using your favorite IoC container Mock Objects Integration AtUnit integrates with JMock or EasyMock to provide mock objects: * obtain a JMock context simply by declaring a field * annotate fields with @Mock to obtain JMock or EasyMock mock objects * annotate fields with @Stub to obtain a JMock or EasyMock stub object ... or you can use your own mock objects plug-in with two easy steps: * implement the MockFramework interface * annotate your tests with @MockFrameworkClass(MyMockFramework.class) Container Integration 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! * @Inject test class fields without even defining a Module * 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 @Bean to get them from the Spring context * fields annotated with @Bean which do not appear in your Spring context are added to it automatically! (This includes @Mock and @Stub fields.) * 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)

The mock-object testing pattern has commonly been used to test an individual unit of code without testing its dependencies. While this pattern works well for interaction-based testing, it can be overkill for state-based testing. Learn how to streamline your unit-testing using stubs and the pseudo-objects testing pattern.

To someone who is new to unit testing, the idea of mock objects can be confusing to say the least. I have covered in previous tutorials how to use various mock object frameworks (EasyMock and jmockit). However in this tutorial, we will focus on the concept of mocking in general. What is a mock object? What is it used for? Why can't I mock object XYZ? Let's look into these questions and maybe clear a bit of the air on the use of mock objects.

This library allows you to use JavaBeans-style property matching for arguments when using EasyMock. Property matching is based on commons-beanutils as documented in Standard JavaBeans.