A mechnism for using a test class as the manifest for isolating the context of a test. Thereby using the same di mechanism you would expect in production but fully controlled to isolate the variable under test.
Release date: 10 August 2011
Files: 22,
Classes: 22,
Lines of code: 1111
Google AppEngine:
Partial support
Depends on:(View as diagram)
-
Maven-Central / javax.inject / javax.inject
-
Maven-Central / net.stickycode / sticky-coercion
-
Maven-Central / net.stickycode / sticky-coercion-api
-
Maven-Central / net.stickycode / sticky-exception
-
Maven-Central / net.stickycode / sticky-reflector
-
Maven-Central / net.stickycode / sticky-stereotype
-
Maven-Central / net.stickycode.configured / sticky-configured
-
Maven-Central / net.stickycode.configured / sticky-configured-api
-
Maven-Central / net.stickycode.mockwire / sticky-mockwire-api
-
Used by:
-
Maven-Central / net.stickycode.mockwire / sticky-mockwire-guice3
MD5 Signatures:
- 2419da676a0f06c060fd653a06a2ba4d
- ac2adde0a13ab67f70bae5bf5fd9bbf7
