My two cents: If we add Mockito then we should have sound integration tests. Unit tests that "smoke test" public methods are not enough.
Mocks are great at making assumptions - which is nice - but to be confident, integration tests that are properly set up and teared down will give us great coverage. On Sun, Jun 11, 2017, 10:43 Edward Capriolo <[email protected]> wrote: > I am not a strong believer in mockito. Generally i believe that if you > design things well you need less / no mockink. > > That said. Moving the end to end test to thier own module lowered code > coverage. > > running mvn cobertura:cobertura and adding unit/mock tests to increase > coverage is a good idea. > > Thus far we have added interfaces and extend/ implement as mock alternative > > On Saturday, June 10, 2017, Terry Weymouth <[email protected]> wrote: > > > Any experience with Mockito in the incubator-gossip context out there? > > In brief, I am looking for pom entry(s) and/or example code, and any > other > > guidance, > > to short-circuit the normal stumbling around to get the first try right. > > > > -- > Sorry this was sent from mobile. Will do less grammar and spell check than > usual. >
