You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by Harald Wellmann <hw...@gmail.com> on 2015/06/15 20:12:14 UTC
Broken Arquillian tests don't fail
At the moment, quite a few Arquillian tests are broken but don't fail
the build.
Above all, this affects the Weld profile where the weld-core dependency
seems to be missing. In the OWB profile, there are some broken tests in
the JSF Impl module. I didn't check the app server profiles, the
standalone ones look bad enough...
Arquillian 1.1.4 bails out but does not fail the build when the test
deployment cannot be deployed.
This is fixed in Arquillian 1.1.8, i.e. deployment errors will fail the
tests.
Thus, I propose to upgrade to Arquillian 1.1.8 (after the DS 1.4.1
release) and then to work on fixing all those broken tests.
Best regards,
Harald
Re: Broken Arquillian tests don't fail
Posted by Gerhard Petracek <ge...@gmail.com>.
hi harald,
thx! the weld profile looks fine now (for v1.x and v2.x).
however, now we have an issue with our arquillian-drone based tests as well
as with the build-config for weld3.
regards,
gerhard
2015-06-16 11:57 GMT+02:00 Harald Wellmann <hw...@gmail.com>:
> Should be fixed now, both for OWB and Weld, see
> https://issues.apache.org/jira/browse/DELTASPIKE-929 and 933.
>
> Regards,
> Harald
>
>
> Am 15.06.2015 um 22:29 schrieb Gerhard Petracek:
>
>> hi harald,
>>
>> once i change one of the assert-statements, the corresponding test fails
>> (as expected).
>> (tested with the owb-profile - via a simple mvn clean install)
>>
>> + the number of (executed) tests look fine as well
>> (if you exclude the tests with category EnterpriseArchiveProfileCategory,
>> FullProfileCategory, WebEE7ProfileCategory and WebProfileCategory).
>>
>> -> it would be great if you can tell us the jdk-version you are using (we
>> saw arquillian-issues with some versions in the past).
>>
>> however, i see an issue with the weld-profile as well - obviously not all
>> tests get executed.
>>
>> regards,
>> gerhard
>>
>>
>>
>> 2015-06-15 21:13 GMT+02:00 Harald Wellmann <hw...@gmail.com>:
>>
>> These are the OWB tests that fail with Arquillian 1.1.8:
>>>
>>> Tests in error:
>>>
>>>
>>> org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc002.StaticNavigationParameterWarFileTest:
>>> Arquillian has previously been attempted initialized, but failed. See
>>> cause
>>> for previous exception
>>>
>>>
>>> org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc004.DynamicNavigationParameterWarFileTest:
>>> Could not create new instance of class
>>> org.jboss.arquillian.test.impl.EventTestRunnerAdaptor
>>>
>>>
>>> org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc001.NoNavigationParameterWarFileTest:
>>> Arquillian has previously been attempted initialized, but failed. See
>>> cause
>>> for previous exception
>>>
>>> These seem to be caused by a Xerces version mismatch:
>>>
>>> Caused by: java.lang.ClassNotFoundException: org.w3c.dom.ElementTraversal
>>>
>>> With Weld, it looks like _all_ Arquillian tests are currently failing.
>>>
>>> Regards,
>>> Harald
>>>
>>>
>>>
>>
>
Re: Broken Arquillian tests don't fail
Posted by Harald Wellmann <hw...@gmail.com>.
Should be fixed now, both for OWB and Weld, see
https://issues.apache.org/jira/browse/DELTASPIKE-929 and 933.
Regards,
Harald
Am 15.06.2015 um 22:29 schrieb Gerhard Petracek:
> hi harald,
>
> once i change one of the assert-statements, the corresponding test fails
> (as expected).
> (tested with the owb-profile - via a simple mvn clean install)
>
> + the number of (executed) tests look fine as well
> (if you exclude the tests with category EnterpriseArchiveProfileCategory,
> FullProfileCategory, WebEE7ProfileCategory and WebProfileCategory).
>
> -> it would be great if you can tell us the jdk-version you are using (we
> saw arquillian-issues with some versions in the past).
>
> however, i see an issue with the weld-profile as well - obviously not all
> tests get executed.
>
> regards,
> gerhard
>
>
>
> 2015-06-15 21:13 GMT+02:00 Harald Wellmann <hw...@gmail.com>:
>
>> These are the OWB tests that fail with Arquillian 1.1.8:
>>
>> Tests in error:
>>
>> org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc002.StaticNavigationParameterWarFileTest:
>> Arquillian has previously been attempted initialized, but failed. See cause
>> for previous exception
>>
>> org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc004.DynamicNavigationParameterWarFileTest:
>> Could not create new instance of class
>> org.jboss.arquillian.test.impl.EventTestRunnerAdaptor
>>
>> org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc001.NoNavigationParameterWarFileTest:
>> Arquillian has previously been attempted initialized, but failed. See cause
>> for previous exception
>>
>> These seem to be caused by a Xerces version mismatch:
>>
>> Caused by: java.lang.ClassNotFoundException: org.w3c.dom.ElementTraversal
>>
>> With Weld, it looks like _all_ Arquillian tests are currently failing.
>>
>> Regards,
>> Harald
>>
>>
>
Re: Broken Arquillian tests don't fail
Posted by Gerhard Petracek <ge...@gmail.com>.
hi harald,
once i change one of the assert-statements, the corresponding test fails
(as expected).
(tested with the owb-profile - via a simple mvn clean install)
+ the number of (executed) tests look fine as well
(if you exclude the tests with category EnterpriseArchiveProfileCategory,
FullProfileCategory, WebEE7ProfileCategory and WebProfileCategory).
-> it would be great if you can tell us the jdk-version you are using (we
saw arquillian-issues with some versions in the past).
however, i see an issue with the weld-profile as well - obviously not all
tests get executed.
regards,
gerhard
2015-06-15 21:13 GMT+02:00 Harald Wellmann <hw...@gmail.com>:
> These are the OWB tests that fail with Arquillian 1.1.8:
>
> Tests in error:
>
> org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc002.StaticNavigationParameterWarFileTest:
> Arquillian has previously been attempted initialized, but failed. See cause
> for previous exception
>
> org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc004.DynamicNavigationParameterWarFileTest:
> Could not create new instance of class
> org.jboss.arquillian.test.impl.EventTestRunnerAdaptor
>
> org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc001.NoNavigationParameterWarFileTest:
> Arquillian has previously been attempted initialized, but failed. See cause
> for previous exception
>
> These seem to be caused by a Xerces version mismatch:
>
> Caused by: java.lang.ClassNotFoundException: org.w3c.dom.ElementTraversal
>
> With Weld, it looks like _all_ Arquillian tests are currently failing.
>
> Regards,
> Harald
>
>
Re: Broken Arquillian tests don't fail
Posted by Harald Wellmann <hw...@gmail.com>.
These are the OWB tests that fail with Arquillian 1.1.8:
Tests in error:
org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc002.StaticNavigationParameterWarFileTest:
Arquillian has previously been attempted initialized, but failed. See
cause for previous exception
org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc004.DynamicNavigationParameterWarFileTest:
Could not create new instance of class
org.jboss.arquillian.test.impl.EventTestRunnerAdaptor
org.apache.deltaspike.test.jsf.impl.config.view.navigation.parameter.uc001.NoNavigationParameterWarFileTest:
Arquillian has previously been attempted initialized, but failed. See
cause for previous exception
These seem to be caused by a Xerces version mismatch:
Caused by: java.lang.ClassNotFoundException: org.w3c.dom.ElementTraversal
With Weld, it looks like _all_ Arquillian tests are currently failing.
Regards,
Harald
Re: Broken Arquillian tests don't fail
Posted by Gerhard Petracek <ge...@gmail.com>.
hi harald,
+1
can you please send a list of the affected tests (upfront).
regards,
gerhard
2015-06-15 20:12 GMT+02:00 Harald Wellmann <hw...@gmail.com>:
> At the moment, quite a few Arquillian tests are broken but don't fail the
> build.
>
> Above all, this affects the Weld profile where the weld-core dependency
> seems to be missing. In the OWB profile, there are some broken tests in the
> JSF Impl module. I didn't check the app server profiles, the standalone
> ones look bad enough...
>
> Arquillian 1.1.4 bails out but does not fail the build when the test
> deployment cannot be deployed.
>
> This is fixed in Arquillian 1.1.8, i.e. deployment errors will fail the
> tests.
>
> Thus, I propose to upgrade to Arquillian 1.1.8 (after the DS 1.4.1
> release) and then to work on fixing all those broken tests.
>
> Best regards,
> Harald
>
>
Re: Broken Arquillian tests don't fail
Posted by Romain Manni-Bucau <rm...@gmail.com>.
+1
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
2015-06-15 20:35 GMT+02:00 Thomas Andraschko <an...@gmail.com>:
> +1
>
> 2015-06-15 20:12 GMT+02:00 Harald Wellmann <hw...@gmail.com>:
>
> > At the moment, quite a few Arquillian tests are broken but don't fail the
> > build.
> >
> > Above all, this affects the Weld profile where the weld-core dependency
> > seems to be missing. In the OWB profile, there are some broken tests in
> the
> > JSF Impl module. I didn't check the app server profiles, the standalone
> > ones look bad enough...
> >
> > Arquillian 1.1.4 bails out but does not fail the build when the test
> > deployment cannot be deployed.
> >
> > This is fixed in Arquillian 1.1.8, i.e. deployment errors will fail the
> > tests.
> >
> > Thus, I propose to upgrade to Arquillian 1.1.8 (after the DS 1.4.1
> > release) and then to work on fixing all those broken tests.
> >
> > Best regards,
> > Harald
> >
> >
>
Re: Broken Arquillian tests don't fail
Posted by Thomas Andraschko <an...@gmail.com>.
+1
2015-06-15 20:12 GMT+02:00 Harald Wellmann <hw...@gmail.com>:
> At the moment, quite a few Arquillian tests are broken but don't fail the
> build.
>
> Above all, this affects the Weld profile where the weld-core dependency
> seems to be missing. In the OWB profile, there are some broken tests in the
> JSF Impl module. I didn't check the app server profiles, the standalone
> ones look bad enough...
>
> Arquillian 1.1.4 bails out but does not fail the build when the test
> deployment cannot be deployed.
>
> This is fixed in Arquillian 1.1.8, i.e. deployment errors will fail the
> tests.
>
> Thus, I propose to upgrade to Arquillian 1.1.8 (after the DS 1.4.1
> release) and then to work on fixing all those broken tests.
>
> Best regards,
> Harald
>
>