[jboss-as7-dev] testsuite

[Kabir Khan]

On 14 Feb 2011, at 15:19, Brian Stansberry wrote:

> On 2/14/11 9:08 AM, ssilvert at redhat.com wrote:
>> I see that there's not that much in there right now.  Am I free to add
>> a JSF test module to testsuite or are we putting component tests
>> somewhere else?
>> 
> 
> Yes, you can add things. They should test more than the internals of a 
> module to go in testsuite though; stick internal module testing in the 
> module itself.
> 
> There are a few submodules under testsuite; most likely stuff will go in 
> integration or smoke. Smoke runs every time someone builds, unless you 
> do -DskipTests=true, so don't stick stuff in there unless its important 
> to fail the build if the test breaks.
> 
>> Also, is there any documentation on using the arquillian module that
>> is there in the as7 build?
>> 
> 
> I don't think so, although Kabir and Thomas often surprise me. :) Most 
> of the tests in testsuite/smoke use the arquillian modules though.


The smoke tests still mainly use plain surefire which currently relies on the classpath to bootstrap the test, then uses modules to bootstrap the AS. So whatever is inside AS uses modular classloading.

The forked surefire plugin (http://community.jboss.org/wiki/JBossModulesSurefirePlugin) allows using modules to bootstrap the test, meaning the test is fully modular. This is currently used for ServerInModuleStartupTestCase. I have some code to bootstrap Arquillian fully embedded using the plugin, but I have not put that in yet, since our demos have been quite unstable the past 1.5 months with 2 major refactorings going on. Once I've finished the bulk of my work on the domain stuff (hopefully later this week) I plan on revisiting this, and using the fully modular environment for the current smoke tests.