Don't run your command-line tool in +initialize. That's sent by the Objective-C runtime when the class is first sent any message.
Instead, run your command-line tool in your test's +setUp
method. (Note that I really did mean +setUp
and not -setUp
; lots of folks seem to be a bit fuzzy on the difference between class and instance methods.)
In this case, a class setUp
method is invoked by OCUnit before any of tests in a SenTestCase
subclass are run, and a class tearDown
method is invoked by OCUnit after all tests in a SenTestCase
subclass ar run.
So the overall flow for a particular SenTestCase
subclass is:
- send
+setUp
to SomeTestCase
- for each
test
method starting in SomeTestCase
(call it test___
)
- create a new instance of
SomeTestCase
- send
-setUp
to it
- send
-test___
to it
- send
-tearDown
to it
- release it
- send
+tearDown
to SomeTestCase
This way if you have something that needs to be done before any of your -test
methods run, or something that needs to be done after all of your -test
methods run, there's a deterministic point at which you can make that happen. (Rather than rely on memory management, which isn't deterministic in the same way, and may not be deterministic at all if you're using GC.)
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…