[arquillian-issues] [JBoss JIRA] Commented: (ARQ-296) Arquilian should fail gracefully when no container is present
Dan Allen (JIRA)
jira-events at lists.jboss.org
Wed Sep 15 03:52:28 EDT 2010
[ https://jira.jboss.org/browse/ARQ-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12550997#action_12550997 ]
Dan Allen commented on ARQ-296:
-------------------------------
You can duplicate this issue in the examples/junit by first removing the link <skip>true</skip> from the pom.xml, then running:
mvn test -Dtest=RandomTestCase
cat target/surefire-reports/*RandomTestCase*.txt
> Arquilian should fail gracefully when no container is present
> -------------------------------------------------------------
>
> Key: ARQ-296
> URL: https://jira.jboss.org/browse/ARQ-296
> Project: Arquillian
> Issue Type: Bug
> Components: Deployable Containers SPI
> Affects Versions: 1.0.0.Alpha4
> Reporter: Dan Allen
> Fix For: 1.0.0.Beta1
>
>
> Currently, if a container is not on the classpath when the test suite is executed, Arquillian fails with a NullPointerException:
> java.lang.NullPointerException
> at org.jboss.arquillian.impl.DeployableTestBuilder.build(DeployableTestBuilder.java:88)
> at org.jboss.arquillian.impl.DeployableTestBuilder.build(DeployableTestBuilder.java:77)
> at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:93)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31)
> at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
> at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
> Arquillian should instead fail the test, reporting that no container implementation is present on the classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the arquillian-issues
mailing list