andrei-tara / dirty-mockito Goto Github PK

Version: 0.2

I've been looking around for something that integrates Spring and Mockito,
and this is an interesting approach.

I think it could be evolved to be more generally useful.

For example, I want to use a mock bean to test that my ReSTful web app is
calling the correct methods, and responding correctly to exceptions.

In this case, the mock needs to be available to the WebApplication context,
and it Mockito.reset(T ... mocks) needs to be called between each test.

Yesterday I ran into a problem:

class A {
  @EJB B b;
}

class B {
  @Resource C c;
}

Testing "A" I can just mock for "B" (using your example code) but because "B" 
needs "C" I can't run the test without NullPointerException.

So I wish it could be possible to handle this kind behaviour.

Sometimes it is possible to use a Mockito.spy() instead of Mockito.mock() - if 
you need mostly the orginal methods but mock just a few of them. In this case 
it would be nice to have an annotation like this:

public class ATest extends ActiveTest<B> {

  @Mock
  private EntityManager em;

  @Spy
  private SomeService service = new SomeService();
...
  // mock just one method
  when(service.doIt()).thenReturn(result);

  // it calls doIt()
  service.doItNow();

  verify(service).doIt();
...

It should be part of the automatic injection too (like @Mock).

Reason: It'd be nice to use dirty-mockito a bit more widely, but adding a 
repository that can disappear is often not allowed on significant open source 
and commercial projects.

I recently jumped through this hoop, and it wasn't as challenging as I'd 
feared.  Sonatype were very quick in setting up the staging repository and it 
just took me a few iterations to pass the quality checks (i.e. that I was 
providing sources, and javadoc).

If you'd like some help, then I'd be happy to oblige.