Multiple SenTestCase Classes makes test rig fail with code 139?
Multiple SenTestCase Classes makes test rig fail with code 139?
- Subject: Multiple SenTestCase Classes makes test rig fail with code 139?
- From: "Tim M. Madsen" <email@hidden>
- Date: Thu, 2 Apr 2009 14:30:27 +0200
Hi guys, this is my first post on the list, so please be gentle :)
I'm doing some unit testing using the SenTestingKit framework on a project that I'm doing for iPhone OS 2.2. I wrote my first class SenTestCase without a hitch, and though this was gold. The next SenTestCase class I wrote made the rig crash with a code 139, which has now bugged me for two days. I have been over the code again and again, as I read somewhere that it might be a result of poor memory management, which is likely since this is the first time I try and program in a manually managed memory environment.
So five minutes ago, I removed one of the SenTestCase classes from my unit test target, and the one test class left in the target did allright. Then I tried swapping them, and the other test class also ran fine. 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.
_______________________________________________
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