Guice injector in JUnit tests

java junit guice code-injection
Alexis Dufrenoy picture Alexis Dufrenoy · Apr 12, 2011 · Viewed 53.8k times · Source

Using Guice, is it a good practice to get a new injector in each JUnit test class, as each test class should be independant?

Answer

Michael Lloyd Lee mlk picture Michael Lloyd Lee mlk · Apr 12, 2011

You should really avoid using Guice in unit tests as each test should be small enough that manual DI is manageable. By using Guice (or any DI) in unit tests you are hiding away a warning that your class is getting too big and taking on too many responsibilities.

For testing the bootstrapper code and integration tests then yes create a different injector for each test.

Related questions

Mock a superclass constructor

I would like to know if I can mock a super class constructors call and its super() calls. For example, I have the following classes class A { A(..) { super(..) } } class B extends A { B(C c) { super(c) } } So, I …

Read More
How do you assert that a certain exception is thrown in JUnit 4 tests?

How can I use JUnit4 idiomatically to test that some code throws an exception? While I can certainly do something like this: @Test public void testFooThrowsIndexOutOfBoundsException() { boolean thrown = false; try { foo.doStuff(); } catch (IndexOutOfBoundsException e) { thrown = true; } assertTrue(thrown); } I …

Read More
Mockito : how to verify method was called on an object created within a method?

I am new to Mockito. Given the class below, how can I use Mockito to verify that someMethod was invoked exactly once after foo was invoked? public class Foo { public void foo(){ Bar bar = new Bar(); bar.someMethod(); } } I would …

Read More