Well, yeah, but like you've already said, that can be verified by inOrder :)
To sum up: me and other members of my team are really satisfied with FlexUnit / Mockito combo. I feel pretty confident that one can write any reasonable unit test using those frameworks. I definitely don't like idea of having more frameworks allowed as it results in tests suites which are harder to maintain and more complicated build. But that's of course only my two cents, I'm not even commiter so feel free to ignore me ;) 2012/2/9 Martin Heidegger <m...@leichtgewicht.at>: > On 10/02/2012 03:25, Piotr Kawiak wrote: >> >> Magic string methods are not cool. Much better to have code completion >> / refactoring support. Mockito works great for me. What do you mean by >> 'checks if there was _any_ execution of this method call' ? >> > In mockito: if you have something like that > > doSomething(mock); > > and internally it does something like > > mock.a(); > mock.b(); > mock.c(); > > and you test it with > > verify().that(mock.a()); > > then it will pass, even though b was called before that. > I prefer to test my things for a particular call order as it is stricter. > > yours > Martin.
