[wildfly-dev] Test run with standalone-jbossweb configuration
Tomaž Cerar
tomaz.cerar at gmail.com
Tue Jun 18 11:07:21 EDT 2013
Hi,
given that many tests rely on manipulating subsystem resources/operations
that are specific to undertow subsystem (and used to be specific to web
subsystem)
It is expectable that if you would run testsuite with web subsystem instead
of undertow that some of those tests would fail.
--
tomaz
On Tue, Jun 18, 2013 at 2:20 PM, Chao Wang <chaowan at redhat.com> wrote:
> Hey all,
>
> For the tests inside wildfly/web, currently they run peacefully with
> undertow (all passed). However, if I change the test Config file
> arquillian.xml and switch serverConfig back to standalone-jbossweb.xml
> to run them? I got an unexpected failures list:
>
>
> Tests run: 209, Failures: 10, Errors: 95, Skipped: 9
>
> The line I changed in integration/basic/src/test/config/arq/arquillian.xml
> :
>
> <property
> name="serverConfig">${jboss.server.config.file.name:
> standalone.xml}</property>
>
>
> modify to:
>
> <property name="serverConfig">standalone-jbossweb.xml</property>
>
> Then inside /testsuite, run $ mvn clean install -Dts.noSmoke -Dts.basic
>
> Is this reasonable action to switch server configuration file for tests
> like this? Or an expected result and its forbidden to make such change?
>
> Thanks,
>
> Chao
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20130618/0374cf54/attachment.html
More information about the wildfly-dev
mailing list