Re: Multiple SenTestCase Classes makes test rig fail with code 139?
Re: Multiple SenTestCase Classes makes test rig fail with code 139?
- Subject: Re: Multiple SenTestCase Classes makes test rig fail with code 139?
- From: Andrew Pontious <email@hidden>
- Date: Sat, 11 Apr 2009 22:55:02 -0700
On Apr 2, 2009, at 5:30 AM, Tim M. Madsen wrote:
[snip]
So my question is this: am I not supposed to create multiple classes
with tests? Should I place all the tests in one class? Or
instantiate test class from a single class? Something like that, or
do I probably just have a memory bug lurking in the shadows? As I
said, this has been buggin me for two straight days, where I have
gone over the code multiple times, and I can't see where I'm doing
anything wrong. Any help will be appreciated.
There should be no problem with creating multiple classes with tests
-- the projects I work I do this without a hitch.
So there is something going on more specific to your tests.
A very general way to debug this would be to remove code from one of
the tests until you don't see a problem anymore.
Another way would be to add logging statements into your tests, so
that you see the exact point of failure (i.e. what the last log
statement is).
-- Andrew
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden