RE: [MO-java-dev] DynaMock proxy toString issue

[Tim M. <tim...@po...>]

> Alternatively I would suggest not using mocks to test Mock, I don't think
> you need to. I think plain old fashioned exo-testing would cut it. This
> would have the advantage of providing examples of usage and
> decoupling the
> test from implementation, making it simpler to integrate with Nat's

I can comment that Nat and I tried that when we redid the current version
test first - and the tests we were writing were very hard and not driving
our design. We took the stance that we would use the old mock
implementations to help, and this gave us a huge productivity boost (we
decided not to use dynamics to test dynamics as that is a brain bender) -
honest. We also found that using mock maker was a big time saver too (hand
coding some of our interface changes was just too painful as well).


Tim
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.490 / Virus Database: 289 - Release Date: 16/06/2003