Attempting to use OCUnit for some obj-c unit testing. When I follow Apple's HOWTO at Adding Unit Tests to Your Projects it looks like OmniBase/OBPostLoader.m, line 494 is causing the OCUnit framework to fail.

ASSERT failed: requires 'MethodSignatureConflictCount == 0', file /Users/tanner/projects/xcode/OmniGroup/Frameworks/OmniBase/OBPostLoader.m, line 494
You have 15 seconds to attach to pid 8465 in gdb...
/Developer/Tools/RunPlatformUnitTests.include: line 236:  8465 Abort trap              "${TEST_HOST}" ${TEST_HOST_FLAGS} ${OTHER_TEST_FLAGS}
/Developer/Tools/RunPlatformUnitTests.include:304: error: Test host '/Users/tanner/projects/xcode/MetaBiff/build/Debug/MetaBiff.app/Contents/MacOS/MetaBiff' exited abnormally with code 134 (it may have crashed).

If I comment out the offending line of code:

    // We should find zero conflicts!
    //OBASSERT(MethodSignatureConflictCount == 0);

Everything works as expected.

I"m pretty new to Xcode and OCUnit, but the last bit of the logs show OmniBase as the potential problem, so I'm starting here.

[Tim Wood]

We set up unit tests to fail if there are assertion failure. You are hitting one in OmniBase when it is doing some runtime checks of ObjC method signature conflicts, so really you will likely want to investigate those and fix them.