[Dev] functional testing prep work

[Donn Denman]

Would this option allow committing changes to both CATS and Chandler  
at the same time?  Currently there's a problem -- we can't keep CATS  
totally in sync with Chandler, e.g. when we change a Block name  
that's referenced in a CATS script.


On Aug 30, 2005, at 1:06 PM, Mike Taylor wrote:

> It isn't optional and at the current time I don't think that is a  
> big concern.  The functional tests and their support files are very  
> small and not that many.  Later as the scope or depth of functional  
> testing changes then updated can be made.
>
>
> On Aug 30, 2005, at 2:46 PM, Phillip J. Eby wrote:
>
>
>> At 02:23 PM 8/30/2005 -0400, Mike Taylor wrote:
>>
>>>  - add a svn:exernal "link" to chandler/tools/ directory that  
>>> points to http://svn.osafoundation.org/qa/chandler/CATS/  
>>> repository.  This will allow any chandler checkout to also grab  
>>> the required files to run the functional tests.
>>>
>>
>> Won't this force the grabbing?  i.e., I don't think svn:externals  
>> is optional.
>>
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> Open Source Applications Foundation "Dev" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/dev
>>
>>
>>
> ---
> Bear
>
> Build and Release Engineer
> Open Source Applications Foundation (OSAF)
> bear at osafoundation.org
> http://www.osafoundation.org
>
> bear at code-bear.com
> http://code-bear.com
>
> PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev
>