Author: gpetracek
Date: Thu May 15 15:46:21 2014
New Revision: 1594953
URL: http://svn.apache.org/r1594953
Log:
updated content
Modified:
deltaspike/site/trunk/content/test-control.mdtext
Modified: deltaspike/site/trunk/content/test-control.mdtext
URL:
http://svn.apache.org/viewvc/deltaspike/site/trunk/content/test-control.mdtext?rev=1594953&r1=1594952&r2=1594953&view=diff
==============================================================================
--- deltaspike/site/trunk/content/test-control.mdtext (original)
+++ deltaspike/site/trunk/content/test-control.mdtext Thu May 15 15:46:21 2014
@@ -220,7 +220,6 @@ Using a mocking framework makes no diffe
Since CDI implementations like OpenWebBeans use a lot of optimizations, it's
required to handle mocks for application-scoped beans differently - e.g.:
-However, `ApplicationMockManager` can be used for adding all mocks, if they
should be active for the lifetime of the CDI-container.
:::java
@RunWith(CdiTestRunner.class)
@@ -261,6 +260,8 @@ However, `ApplicationMockManager` can be
}
}
+However, `ApplicationMockManager` can be used for adding all mocks, if they
should be active for the lifetime of the CDI-container.
+
It's also possible to mock qualified beans. Just add the literal-instance(s)
as additional parameter(s) - e.g.:
:::java
