objective c - OCUnit Tests giving errors in classes not being tested -

I've written an OCUnet test, which was fine in Xcode 3.2, and now I have problems with Xcode 4 with it Checks in a single stable function in X class a , which does not call any class or function (outside of library work). Only one other code that needs to be called is a stable constructor, which introduces two fixed variables, but then, they are hardcoded values ​​(arrays) that do not call any other class, or class A .

And yet, to solve me , for all classes M, .m, and. C files included, _OBJC_CLASS _ $ _ ClassB ", referenced from: Errors. I do not remember that Xcode has any of 3, but OK, there is no problem, let me compile it Class B 's + [B initialize] .

Why is not a reference made in a way called a class on a stable manufacturer? Can I fix this, ideally to adjust my class without any tests?

update

To know what is going on next, test cases and #import "ah" to see what will happen Mple unit tests:

  - (zero) test some {STAssertTrue (no, @ "did this work?");}   
  still  Is called my  + [B initialize]  and fails. It seems that the oscillate is crawling in all my classes, and they get their  + initialize  methods in this process It does not make sense to me - How can I disable this behavior?  
 My stick trace is already called by my code, if it helps:  
  # 7 _class_initialize () # 8 prepareForMethodLookup () # 9 lookUpMethod ( ) # 10 + [NSBJECT (SENASTTUNTUMULTISES) senIsASuperclassOfClass:] () # 12 + [NSBJT (SNATTTUtilities) from San JoseScience] () # 13 + [Sennetship Update Cache] () # 14 + [SenTestSuite suiteForBundleCache] () # 15 + [SenTestSuite testSuiteForBundlePath:] () # 16 + [SenTestProbe specifiedTestSuite] () # 17 + [SenTestProbe runTests:] () # 18 & LT; Line & Gt; () # 19 & lt; Line & Gt; () # 20 & lt; Line & Gt; () # 21 & lt; Line & Gt; ()    
 
 
 I have a number of problems with xcode 4 and my unit testing suites Did as well well.  
 I know that in order to know what is going on in your case I will have to look at my source, but OCUnit does a lot of things through reflection on sections, similarly with "test" It tells this figure to run the starting methods, then it makes sense in some sense that it is inspecting its classes, because its class initializers fire.  
 I know that this is probably not the answer to this question you are seeing, but if errors are introduced in BK + because this application is dependent on some type of application state, you really Thinking about reconstruction can start +. For this exact reason, the square should not be dependent on anything outside ... you have no guarantees when it will be active or in what state things will happen.