Re: Unit testing framework suggestions?
Re: Unit testing framework suggestions?
- Subject: Re: Unit testing framework suggestions?
- From: Georg Tuparev <email@hidden>
- Date: Sun, 26 Sep 2004 01:41:50 +0200
On Sep 24, 2004, at 2:51 PM, Marco Scheurer wrote:
Yes, that was what I thought. It wouldn't be too hard to use e.g.
the preprocessor to remove these tests from the class for the final
production build. Since I know that I prefer things that are related
(like code and the tests that go with it, or code and its
documentation) together in one file, because otherwise it's too easy
to have them go out of sync.
Not really if you run your tests after each change, or frequently (at
least daily). A lot of our users actually prefer to keep the tests
separated from the code, in a different target or a different project.
Why?
One reason is to avoid deploying the test code and the testing
framework (although I think that in some cases it can be nice to be
able to run the tests at the customer's site).
Some cases? Always! This saved us many debugging hours. And users are
in general impressed. When they see that your program has 3000 tests,
they are really impressed! And because we test UI too, they think it is
fun too - too see all these windows hopping around. BTW, we had one
client who told us to keep the tests always on. This "helped him to
understand better developers intentions"...
Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden