geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Dillon <>
Subject Re: Do we need selenium as part of test support?
Date Thu, 14 Dec 2006 06:09:02 GMT
No, nothing selenium-related needs to be in testsupport.  testsupport  
is mean to hold commonly used code for *unit tests*, and is intended  
to be a dependency of all modules (its already a dependency of some).

If there needs to be some testsuite support classes, then we need to  
add a new module to testsuite/* and move this stuff there.

IMO it was a mistake when testsuite/* classes were moved to  
testsupport and these changes should be reverted and/or reimplmeneted  
in a less harmful way.


On Dec 13, 2006, at 10:03 PM, Matt Hogstrom wrote:

> I ran into a problem tonight when upgrading Jetty 6.  Apparently  
> Selenium-server has jetty included in its jar and its Jetty 5.
> I hacked around the problem but it begs the question as to whether  
> we should dump all testing tools into a single framework.  At some  
> point classpaths will continue to get larger and larger and all  
> tests will pay the penalty.
> Could we include the selenium stuff only in modules that require  
> it?  I'm picking on Selenium now so no offense as its the shiny  
> penny.  I understand that being granular can be just as efficient  
> as uber.
> Matt Hogstrom

View raw message