[atunit commit] r29 - wiki

[codesite...@google.com]

Author: logan.johnson
Date: Mon Nov 12 20:24:05 2007
New Revision: 29

Modified:
wiki/AtUnitTest.wiki

Log:
Edited wiki page through web user interface.

Modified: wiki/AtUnitTest.wiki
==============================================================================
--- wiki/AtUnitTest.wiki (original)
+++ wiki/AtUnitTest.wiki Mon Nov 12 20:24:05 2007
@@ -1,4 +1,5 @@
#summary A quick guide to the pieces of an AtUnit test
+#labels Featured

=Anatomy of an !AtUnit test=

@@ -60,4 +61,4 @@
* _Mocks_ have strict expectations and can be used to validate interactions.
* _Stubs_ are ignored by the framework and are used to supply
dependencies that are irrelevant to the test.

-!AtUnit examines fields that carry the `@Mock` and `@Stub` annotations
and uses the configured framework to create mock objects to fill those
fields. If you're using a container, these field values will be bound
appropriately within the container so that they can be injected by the
container into other objects. If you are not using a container, or if
these fields are not injected by the container, !AtUnit will inject the
fields itself. This means that in most cases, you need not bother with
container-specific annotations on `@Mock` or `@Stub` fields.
+!AtUnit examines fields that carry the `@Mock` and `@Stub` annotations
and uses the configured framework to create mock objects to fill those
fields. If you're using a container, these field values will be bound
appropriately within the container so that they can be injected by the
container into other objects. If you are not using a container, or if
these fields are not injected by the container, !AtUnit will inject the
fields itself. This means that in most cases, you need not bother with
container-specific annotations on `@Mock` or `@Stub` fields.
\ No newline at end of file