title: Can't test my class in basic Unit Test setup
body: <p>I've successfully added a normal Unit Testing Bundle to my project, <a href="https://developer.apple.com/library/ios/#documentation/DeveloperTools/Conceptual/UnitTesting/02-Setting_Up_Unit_Tests_in_a_Project/setting_up.html" rel="nofollow">following these instructions</a>. I can build and run my test target and the one sample test works fine.</p>
  
  <p>Things start to go downhill when I try to test a specific class.</p>
  
  <p>In my App, many of my .h files are included in the .pch file. Also, MyModel interacts with other classes. Because of this, when I import MyModel.h and use it in my test, I get a bunch of errors pertaining to the fact that other files couldn't be loaded. My workaround to this is to simply add the same files in my test target's .pch file and also add those files to the test target's "compile sources" list.</p>
  
  <p>So I add those classes to the test target and to the .pch, try to run, and I just end up in an endless loop, always needing to require more files. When I finally add every .m to my project, running the tests still fails spectacularly.</p>
  
  <p>Any idea how I need to set up my project correctly so that I can just simply <code>#import "MyModel.h"</code> into my test file and write/run my tests? Is it possible that my project is configured in a way that will make testing impossible?</p>
  
  <p><strong>Update 1</strong>
  Followed Carl's suggestions but can't get past step 2. I get:</p>
  
  <pre><code>Undefined symbols for architecture i386:
    "_OBJC_CLASS_$_MyModel", referenced from:
        objc-class-ref in BaseUnitTests.o
  ld: symbol(s) not found for architecture i386
  clang: error: linker command failed with exit code 1 (use -v to see invocation)
  </code></pre>
  
  <p>It's at this point where I would then add MyModel.m to "Build Phases/Compile Sources" and go down the endless path of adding every other .m file to the test target's "Compile Sources".</p>