Very cool Roy. Very cool that you posted this; but even
better - your reaction to it. I like your perspective on
the role of TypeMock.
I'm happy to report that we had the same experience with
Isolator. Using it gave us the flexibility of testing
legacy code that was poorly designed with respect to
dependencies.
It gave us an opportunity then to think about why we
needed a product as robust as Isolator. We started
investigating testable designs and am happy to say that
we too are using MVVM w/ WPF and MOQ has been excellent
for us testing these classes.
I'm glad you see these for what they are. Your product
is as close to magic as it gets for unit isolation, but
the goal should be that you don't need magic to test...
just a testable design.
IF they tried TypeMok THEN they PLANNED to move in
"tests direction".
From this conversation it doesn't appears that TM helped
them moving to "agile way".
It appears that TM is obstacle in form of performance
issues when incorporating "one of agile development
aspects".
And that's not "pure awesome", but sign of "some things
to fix".
Free is the driving force behind a lot of the tools I
use. Moq is on my belt, because of the cost (free).
A free version without "power features" would be great.
Beside the reason you mention, it would also give us a
free version to start with that is expandable with the
help of a little money if we notice the need for "power
features". Starting with any of the free versions now
would force us to relearn, and probably rewrite alot, if
we'd find that need for "power features". Also, it would
put you in competition with the free alternatives to
come up with a great api so you'd be the choice for
starters!
how does a free Isolator (IsolatorLite) benefit TM? if
you create IsolatorLite to use a stepping stone to
TDD/agile/etc. then after the client graduates from
IsolatorLite they may move on to another framework like
RM, Moq, etc.
It's great to give back to the community. I'm not
against that. but the business must be able to support
it's staff. that won't happen with a free tool and the
scenario you described above.
the $$$ version would have to have some very powerful
features that would make the cost acceptable to upgrade
instead of switching to a free product.
This email is clearly pro Moq and contra Typemock. The
way you see it is a remarkable case of ignorance. It's
about time to change your biased view of things.