Well, I'm porting existing code with tests, so I would prefer to avoid
changing how they work.
Now I might as well consider it a rewrite…
On 28 October 2014 21:49, Attila Magyar m.magy...@gmail.com wrote:
This is not supported. BabyMock is designed to test the message flow between
objects, and
Damien Pollet wrote
(if it's not there, consider this an official feature request :)
We tried before
(http://forum.world.st/Unifying-Testing-Ideas-tp4726787p4727283.html) but he
wouldn't drink the partial stub koolaid ;)
-
Cheers,
Sean
--
View this message in context:
Hi, I'm porting unit tests to BabyMock2 from another mocking framework
(DoubleAgents from VW).
Some tests wrap an existing domain object in order to exercise some of
its code, while controlling the return value of one of its methods
(one method is stubbed). I'm guessing this is technically
This is not supported. BabyMock is designed to test the message flow between
objects, and not the internal implementation of an object. If the part what
you want to stub out is not a private implementation detail then maybe
extracting it to an object could help, otherwise couldn't you test the
