There is no "quick start" framework for UnitTesting/ modules (like GoogleToolboxForMac.framework)

[GoogleCodeExporter]

If a developer wants to make use of the unit testing additions in GTM, they 
must directly compile and include the 
GTM/UnitTesting modules in their project. It seems that, like the 
GoogleToolboxForMac.framework, there should 
be a parallel GTMTesting.framework so that developers can track GTM's SVN 
trunk/ in their unit testing code.

Use case:
Barry creates a unit testing bundle in a new project. He adds 
GTMTesting.framework as a target dependency of 
the unit testing bundle and adds GTMTesting.framework to the "Link Binary with 
Libraries" build phase of their 
unit testing bundle. GTMTesting.framewok is installed at @rpath (so that it can 
be installed either in an app test 
harness' frameworks directory (i.e. @executable_path/../Frameworks) or directly 
in the unit test bundle (ie. 
@loader_path/../Frameworks), so the Barry adds either 
@executable_path/../Frameworks or 
@loader_path/../Frameworks to the unit test bundle's runpath search path 
depending on whether his unit tests are 
run in an application harness or not.

Barry can now use GTM's unit testing additions in his own unit test code, while 
tracking improvements to GTM's 
unit testing additions via an svn:external.

Resolution of this issue would add a framework new target to GTM. This 
framework would include the 
UnitTesting/ modules and would link SenTestingKit.framework.

Original issue reported on code.google.com by barryw...@gmail.com on 5 Mar 2009 at 10:52

[GoogleCodeExporter]

fyi - For MacOS that could work, but I think you'd still have to link 
SenTestingKit yourself so those headers could 
be found for your code.

Original comment by thoma...@gmail.com on 6 Mar 2009 at 1:16

[GoogleCodeExporter]

1. Yes, I know this would be MacOS only. I understand if that precludes this 
whole discussion.

2. Yes, you'd still have to link SenTestingKit in user code, but the 
GTMTesting.framework (or whatever it's 
called) will also have to link SenTestingKit for the same reason.

3. An other resolution option is to include the UnitTesting stuff in the GTM 
target (along with linking 
SenTestingKit). This would make it very obvious that the framework is not 
intended to be shipped with an 
application. Either approach would be fine with me.

Original comment by barryw...@gmail.com on 6 Mar 2009 at 1:22

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Make a project reference SenTestingKit.framework to see the headers but Do NOT 
link
SenTestingKit?.framework in test-binary that uses
GTMSenTestCase.h/GTMIPhoneUnitTestDelegate.m, or else the 
[GTMIPhoneUnitTestDelegate
runTests] will fail to run any tests. 

Original comment by msud...@gmail.com on 19 Nov 2009 at 1:45