RfC: Test group separation / module reorganisation

Heiko W.Rupp hrupp at redhat.com
Thu Oct 28 18:17:05 UTC 2010


Hi,

currently (nearly) all tests run in the integration.ejb3 group. No matter if those are server side plugins or core domain
or real biz logic.

Tests should imho be separated out in more distinct groups and only run if relevant
e.g. only run UI tests when UI code or code the UI depends on is changed, but not
when e.g. plugin code has changed.

Another aspect to this is that our builds often build a lot of stuff even if no relevant code
has been changed. THis is e.g. the case when a plugin is changed, the UI code needs
no rebuild (and vice versa).

It looks like the issue is not entirely trivial for the automatic testing side, but there is hope:
- http://www.dzone.com/links/sibilla_first_release_experince_a_new_approach_to.html?ref=ps 
 that is by a colleague, Stefano Maestri and seems to analyze the relevant changed path
 and only run relevant tests
- JunitMax ($$-ware) for Eclipse sorts tests according to runtime and likelihood of failing, so that 
 the user gets fast feedback and sees failures in the usual error view

Anyway : server side plugins should move out of enterprise/server to modules/server-plugins
installer should move out of the enterprise/gui into modules/installer and I guess there are
a few more candidates.
John Sanda was also proposing to move the performance testing outside of enterprise/server
into some (more or less) toplevel module.

-- 
Reg. Adresse: Red Hat GmbH, Otto-Hahn-Strasse 20, 85609 Dornach bei München
Handelsregister: Amtsgericht München HRB 153243
Geschaeftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Charles Cachera



More information about the rhq-devel mailing list