[Cosmo-dev] Cosmo Functional Tests

[Mikeal Rogers]

So we would like to merge the Selenium stuff we've done into the  
Cosmo trunk under src/tests/functional/ but before we do I wanted to  
close some outstanding issues with the current tests.

First off, we have copies of all the HTTPTest (Broadsword) stuff over  
in the tools repository. QA has been maintaining those tests in the  
tools repository and we should probably remove the tests ( and  
tools ) that are currently in tests/functional/HTTPTest. Like we have  
discussed before, those tests (and tools) should be treated as an  
external dependency.

Second, Selenium itself should be brought in as an external  
dependency and we should only maintain our tests and user-extensions.  
The problem is that we currently rely on some Selenium API changes  
that Adam made that haven't been merged in to the Selenium project  
yet. For now we can just stick everything, including the Selenium  
source, in tests/selenium and worry about managing the external  
dependency after our patches make it into the Selenium project.

Third, Adam is not a cosmo commiter. Since adam has never actually  
submitted a patch anywhere in the cosmo tree it would be premature to  
nominate him for commiter status but after I commit his selenium  
tests and user-extensions in to the cosmo tree we can call out the  
work that he's done and nominate him if everyone agrees the code  
looks good. We are gearing up to get the Selenium Python RC stuff  
working and although I'll be writing a lot of code on the python end  
Adam is the expert on Selenium Core js code and I would hate to be in  
a position of approving his patches when he flat out knows more than  
me about the selenium core.

-Mikeal