[atunit commit] r28 - wiki

[codesite...@google.com]

Author: logan.johnson
Date: Mon Nov 12 20:21:09 2007
New Revision: 28

Modified:
wiki/AtUnitTest.wiki
wiki/SupportedContainers.wiki
wiki/WhyAtUnit.wiki

Log:
formatting tweaks

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

=Anatomy of an !AtUnit test=

Modified: wiki/SupportedContainers.wiki
==============================================================================
--- wiki/SupportedContainers.wiki (original)
+++ wiki/SupportedContainers.wiki Mon Nov 12 20:21:09 2007
@@ -6,7 +6,7 @@

==Guice==

-To use Guice for dependency injection, annotate your test class with `@Container(Container.Option.GUICE)`:
+To use Guice for dependency injection, annotate your test class with *`@Container(Container.Option.GUICE)`*:

{{{
// ...
@@ -23,7 +23,7 @@

Any test that uses Guice will be instantiated using the Guice
`Injector`. If you are using a [SupportedMockFrameworks mock
framework], any mocks you declare will be bound to their interfaces as
singletons and injected into objects that request those interfaces.

-If a test requires more flexibility in your bindings than is provided
via field annotation-- for instance, if it requires the injection of
some configuration parameters into the test subject-- the test class
may optionally implement `Module`. Any bindings defined in the
`configure` method will be merged with the field bindings and used when
instantiating the test:
+If a test requires more flexibility in your bindings than is provided
via field annotation-- for instance, if it requires the injection of
some configuration parameters into the test subject-- the test class
may optionally implement `Module`. Any bindings defined in the
`configure` method will be merged with the field bindings and used when
instantiating the test:

{{{
// ...
@@ -45,7 +45,7 @@

==Spring==

-To use Spring for dependency injection, annotate your test with `@Container(Container.Option.SPRING)`:
+To use Spring for dependency injection, annotate your test with *`@Container(Container.Option.SPRING)`*:

{{{
package atunit.example;
@@ -64,9 +64,8 @@

By default, !AtUnit will look in the classpath for a Spring XML
context configuration file named after the test class and in the same
package. In the example above, !AtUnit will look in the classpath
`/atunit/example/ExampleSpringTest.xml`. No exception will be thrown
if the XML file is not found, because an XML file is often not needed.

-An alternate location for the XML file may be specified by annotating
the test class with `@Context("/path/to/filename.xml")`
+An alternate location for the XML file may be specified by annotating
the test class with *`@Context("/path/to/filename.xml")`*.

-
-Fields annotated with `@Bean` will be populated from the application
context. By default, they are autowired by type. The `@Bean`
annotation also takes a bean name parameter-- if present, the named
bean will be used to populate the field.
+Fields annotated with *`@Bean`* will be populated from the application
context. By default, they are autowired by type. The `@Bean`
annotation also takes a bean name parameter-- if present, the named
bean will be used to populate the field.

If the test uses a [SupportedMockFrameworks mock object framework],
and has any mock object fields declared, those fields will be populated
by !AtUnit if they are not populated by Spring. If they carry the
`@Bean` annotation, they will be placed into the Spring context for
injection into other objects (using autowiring by type by default). If
no bean name is specified in the annotation, one will be generated.

Modified: wiki/WhyAtUnit.wiki
==============================================================================
--- wiki/WhyAtUnit.wiki (original)
+++ wiki/WhyAtUnit.wiki Mon Nov 12 20:21:09 2007
@@ -1,4 +1,4 @@
-#summary How !AtUnit helps test authors.
+#summary How AtUnit helps test authors.

=Why !AtUnit?=