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.