Dont want to debate here but mocking internals is not really testing - it is ok for external systems cause you dont have the choice most of the time.
What do you want to mock? Maybe it would be easier this way. Le 1 août 2015 17:11, "Alex Gout" <[email protected]> a écrit : > > I can only assume you're talking about integration testing in which case > you shouldn't use mocks (maybe stubs in some cases for example when relying > on 3rd party services). However, for solid unit testing using mocks is not > avoidable. > Your side note illustrates why unit tests are so important. > > On Sat, Aug 1, 2015 at 12:53 AM Romain Manni-Bucau <[email protected]> > wrote: > > > Hi > > > > Le 1 août 2015 03:30, "Alex Gout" <[email protected]> a écrit : > > > > > > Hi, > > > > > > I created JIRA TOMEE-1618. Can someone check and assign to me please? > > > > > > Also a question.. I don't see many unit tests that use mocks, only a few > > > that use easymock. Is it a problem to introduce Mockito? > > > > > > > Why mocking? Just really test :p. Whell behind the joke the reality is a > > mocked test doesnt gives you any guarantee so for me it is like not testing > > anything - sadly speaking from experience. > > > > Side note: arquillian and mvn modules can have additional tests. > > > > > -Alex > >
