[Cosmo-dev] Re: [Scooby-dev] Issue with same tools in multiple products.

[John Townsend]

I agree with Bear on this. I think its premature to promote HTTPTest  
to a separate project and since you have a new framework coming, I  
would wait until that new work is available to establish it as a  
separate project.

One question: Where is the design proposal for this new Testing  
Framework? I don't recall seeing a design proposal on the mailing  
lists for it.

--> towns


On Jun 7, 2006, at 7:13 PM, Mike Taylor wrote:

> I can see the issue you are talking about but I feel another issue  
> will happen if we move the testing tool to a new location.  We  
> would have to treat it like an external project and bring into play  
> all that would entails:
>
> 	- project space (svn, docs, etc)
> 	- release cycle
> 	- testing across all products for each release
> 	- updating Cosmo and Scooby for each new release
>
> Currently I don't know if HTTPTest is ready for that and I wonder  
> if the time spent doing the above equals the time maintaining two  
> copies (knowing that it will be merged later).
>
> Part of my concern is that having it as a standalone project will  
> force Cosmo's HTTPTest to worry about Scooby's HTTPTest  
> requirements and vice-versa and that may be premature.
>
> Once the OSAF Eco-system Testing Tool has been defined and setup as  
> it's own project then I think we can take the two HTTPTest parts  
> and the Chandler test framework part and start figuring out how to  
> merge them.
>
> On Jun 7, 2006, at 9:51 PM, Mikeal Rogers wrote:
>
>> So we have a good problem, well good that we're far enough along  
>> that it is a problem.
>>
>> As we're nearing end to end testing across the products we've  
>> quickly started to use the same tools and frameworks in multiple  
>> products. Since traditionally our process has been to keep  
>> functional testing tools in each products svn repository we've  
>> encountered some technical and process issues.
>>
>> 1.) People working on a given tool or framework may have different  
>> commit privileges in one product than another.
>> 2.) If a tool or framework is used in two products then we have to  
>> do two separate commits and maintain all the same files in two  
>> repositories.
>>
>> Our current issue is that a tool I originally wrote for cosmo,  
>> HTTPTest, is now being used by adam to develop a tool for scooby  
>> testing, JSONTest. Since it lives in the cosmo repository he can't  
>> commit changes to it and I can't easily merge his changes in while  
>> I'm working on the same files to extend testing for cosmo.
>>
>> Going forward we will be writing a very large framework that will  
>> be used by nearly every tool OSAF QA uses to test all products so  
>> this issue needs to be solved in a broader context than just our  
>> current problem with HTTPTest.
>>
>> I'm open to any and all ideas for solving this problem.
>>
>> -Mikeal
>> _______________________________________________
>> scooby-dev mailing list
>> scooby-dev at lists.osafoundation.org
>> http://lists.osafoundation.org/cgi-bin/mailman/listinfo/scooby-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
>
>
> _______________________________________________
> scooby-dev mailing list
> scooby-dev at lists.osafoundation.org
> http://lists.osafoundation.org/cgi-bin/mailman/listinfo/scooby-dev