[wildfly-dev] Moving component projects to a "feature pack" model?

[Tomaž Cerar]

On Thu, May 28, 2015 at 11:51 PM, Sanne Grinovero <sanne at hibernate.org>
wrote:

> ? How do we test the feature pack ?
>
> The goal of having WildFly use the module structure that we build
> "verbatim" is only interesting if we make sure these packs work
> correctly.
> Ideally we'd like to deploy them in Arquillian tests like we did with
> modules, and run integration tests on each commit.
>


This is quite simple. As part of test run you provision thin WildFly with
your feature pack
and run run arquillian tests. As provisionied server is thin (doesn't
contain any jars) it is also lightweight.

an example would be how we test arquillian integration itself
see for example with provisioning wildfly-core
https://github.com/wildfly/wildfly-arquillian/blob/master/container-managed/pom.xml#L130
or by provisioning wildfly-servlet(aka wildfly-web)
https://github.com/wildfly/wildfly-arquillian/tree/master/container-embedded

Main config is in provisioning configuration
https://github.com/wildfly/wildfly-arquillian/blob/master/container-embedded/embedded-server-provisioning.xml
which can be configured to include as many feature packs as you want.
for example, take wildfly-web(-servlet) distro and add hibernate-search
next to it.

then just run arquillian tests as you would normally do.

We use this in wildfly-core testsuite already (but without arquillain ) and
have plans to move our wildfly full testsuite to use it as well.

--
tomaz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20150529/66194d66/attachment.html