Hi Zoli,
Thanks for the quick reply.
>can you convince us that it is worth to have it?
In general: I just find it hard to imagine a
proper test package without test cases requiring mocking, stubbing, etc. Sure, it depends on the complexity of the product itself, but IncQuery is probably way beyond the level of being easy-to-test w/o supplementary frameworks like Mockito, EasyMock, perhaps PowerMock.
In this specific case: a conflict resolver has to be tested, which requires Activation instances in a ConflictSet. With Mockito, it goes like this:
Activation<?> mock1 = mock(Activation.class);
How would you that w/o a mock framework? Of course, a handful of clever util methods (a.k.a. "the custom testing framework" :) ) could handle this, and maybe there are such methods somewhere deep in IncQuery, but a) I wasn't able to locate them; and b) I just don't see the point to maintain another codebase just for that given the pretty wide selection of quite cool testing frameworks.
Let me mention projects Artop and Sphinx here as the perfect examples in this question. These two are very nicely covered with unit and integration tests, although there is just a ridiculously enormous amount of code dealing with instantiating mock, stub, dummy and fake objects, which could have been clearly avoided by using the proper tools. So I guess it's worth to at least
think about employing Mockito or Easymock in a long-term perspective.
