[Cosmo-dev] Cosmo Functional Tests

[Brian Moseley]

On 10/2/06, Mikeal Rogers <mikeal at osafoundation.org> wrote:

> 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.

please remember to merge in the changes i recently made to the HTTPTest tests.

> 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.

i suggest instead importing selenium into our svn, applying our
patches there, and managing our own build (like we do with ical4j and
jcr-server). that shouldn't take much effort. i'd prefer to avoid
putting the selenium source in the cosmo tree, even as a short term
measure.