Re: Unit testing and Xcode integration
Re: Unit testing and Xcode integration
- Subject: Re: Unit testing and Xcode integration
- From: Tim Hart <email@hidden>
- Date: Sun, 13 Aug 2006 23:44:08 -0500
On Aug 13, 2006, at 10:56 PM, Chris Hanson wrote:
You probably don't really want to simply load your test bundle into a
"test runner" interface and press a button to run your tests. After
all, you can't unload them and re-load them when you change your code.
Instead, what you probably want is to either invoke
/Developer/Tools/otest or /Developer/Tools/RunUnitTests whether from
the command line or from any graphical tool that you may build.
TestKit's Testrunner GUI actually creates a separate process to load
the bundle and run it. This was done intentionally in order to solve
the 'you can't unload and re-load them when you change your code'
problem. You can, in fact, run a bundle from the GUI and watch a test
fail. Then fix the code, re-compile the bundle, and click 'Run' again
from the GUI and watch the test pass this time. The GUI is responding
to DO events from the second process. This other process terminates
once the test run completes, so the bundle is unloaded and reloaded for
every test run.
Tim Hart
_______________________________________________
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