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: 13 November 2011
Files: 22,
Classes: 22,
Lines of code: 1105
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 / org.mockwire / mockwire-guice3
MD5 Signatures:
- 90da9bab93fe50a751eb7af1a05112a8
- b5ac6635ac28be1acda4bebffca079d5
