[JBoss JIRA] (ARQ-1395) CommandBusService is started even tho the test is not a @WarpTest
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1395?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen reopened ARQ-1395:
--------------------------------
Started seeing this. Seem CommandBusService is receiving events from Before/After and trying to push them to the Server.
But since the CommandBusService is not started, the Service URL is not set.
{code}
java.net.MalformedURLException: no protocol: null&operationMode=PUT
at java.net.URL.<init>(URL.java:585)
at java.net.URL.<init>(URL.java:482)
at java.net.URL.<init>(URL.java:431)
at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.execute(CommandEventBus.java:242)
at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.executeCommandRemotely(CommandEventBus.java:220)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.warp.impl.client.eventbus.RemoteSuiteLifecyclePropagation.sendAfter(RemoteSuiteLifecyclePropagation.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103)
at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:245)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
{code}
> CommandBusService is started even tho the test is not a @WarpTest
> -----------------------------------------------------------------
>
> Key: ARQ-1395
> URL: https://issues.jboss.org/browse/ARQ-1395
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Aslak Knutsen
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Alpha3
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> By having Warp on CP, even tho the current test is not marked with @WarpTest, the CommandBusService is still started and attempts to communicate with the server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ARQ-1401) Remove dependency on SLF4J
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1401?page=com.atlassian.jira.plugin.s... ]
Karel Piwko commented on ARQ-1401:
----------------------------------
You made me sad panda :-(. It such case, maybe shading it could help?
Even if I hate shading, I follow the rule that testing framework should have as less dependencies as possible.
> Remove dependency on SLF4J
> --------------------------
>
> Key: ARQ-1401
> URL: https://issues.jboss.org/browse/ARQ-1401
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha6
> Reporter: Karel Piwko
> Assignee: Bartosz Majsak
>
> SLF4J dependency should be removed/replaced with JUL. Current dependency requires projects to add an slf4j compatible implementation into test dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ARQ-1400) Failure to create Enrichment hidden by Client Assertion
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1400?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1400:
----------------------------
Fix Version/s: warp_1.0.0.Alpha3
> Failure to create Enrichment hidden by Client Assertion
> -------------------------------------------------------
>
> Key: ARQ-1400
> URL: https://issues.jboss.org/browse/ARQ-1400
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Aslak Knutsen
> Fix For: warp_1.0.0.Alpha3
>
>
> The chain of event are:
> * Activity is executed
> * Client Request fail to enrich
> * Request goes to server
> * Response comes back
> * Client asserts the Response and fail
> * Exception shown to user is the failed Client side Assertion.
> The real cause of the failure is the failed serialization of the enrichment object to setup the server side, which cause the server side response to be wrong and client assertion of course failing.
> Two things odd here:
> * Enrichment problems are hidden
> * Request still goes to server even tho we couldn't fulfill the setup
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ARQ-1400) Failure to create Enrichment hidden by Client Assertion
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1400?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1400:
----------------------------
Priority: Critical (was: Major)
> Failure to create Enrichment hidden by Client Assertion
> -------------------------------------------------------
>
> Key: ARQ-1400
> URL: https://issues.jboss.org/browse/ARQ-1400
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Aslak Knutsen
> Priority: Critical
> Fix For: warp_1.0.0.Alpha3
>
>
> The chain of event are:
> * Activity is executed
> * Client Request fail to enrich
> * Request goes to server
> * Response comes back
> * Client asserts the Response and fail
> * Exception shown to user is the failed Client side Assertion.
> The real cause of the failure is the failed serialization of the enrichment object to setup the server side, which cause the server side response to be wrong and client assertion of course failing.
> Two things odd here:
> * Enrichment problems are hidden
> * Request still goes to server even tho we couldn't fulfill the setup
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ARQ-1401) Remove dependency on SLF4J
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1401:
--------------------------------
Summary: Remove dependency on SLF4J
Key: ARQ-1401
URL: https://issues.jboss.org/browse/ARQ-1401
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha6
Reporter: Karel Piwko
Assignee: Bartosz Majsak
SLF4J dependency should be removed/replaced with JUL. Current dependency requires projects to add an slf4j compatible implementation into test dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ARQ-1400) Failure to create Enrichment hidden by Client Assertion
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1400?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen commented on ARQ-1400:
------------------------------------
{code}
aslak> lfryc https://github.com/arquillian/continuous-enterprise-development/blob/rel_...
<aslak> tight.. i degraded warp. let me try latest again
<aslak> it's caught in DefaultHttpRequestEnrichmentService.enrichRequest
<aslak> java.lang.IllegalStateException: java.io.NotSerializableException: org.cedj.geekseek.domain.relation.test.model.SourceObject
<aslak> but i can't see it anywhere exposed
<aslak> i see the Assertion error from my code and nothing in the log
<lfryc> aslak: Warp tries to wrap all exceptions and propagate them as a test failure
<lfryc> +1 it could actually print the stack trace
<lfryc> because sometimes more than one side fails.. client/proxy/server
<aslak> DefaultWarpRequestSpecifier.execute()
<aslak> executeWarp.fire(new ExecuteWarp(activity, warpContext));
<aslak> if that line throws an exception, e.g. a Assertion exception (due to the Interspection not being called), then the real cause is hidden
<aslak> if i remove the Assertion exception i can see the original
<lfryc> looking..
<lfryc> aslak: which Assertion exception you are talkinga bout?
<lfryc> it's thrown by you or Warp?
<aslak> me
<aslak> from inside Activity
<lfryc> ic
<lfryc> hmm
<lfryc> the logic should be:
<lfryc> I say "should" because I refactored that way and it's tested that way.. :-)
<lfryc> ... when server fails, then it should be propagated (client exception should be swallowed)
<lfryc> ... when proxy fails, then it should behave same as server
<lfryc> cause when client fails, it's usually because of reaction to server's failure
<lfryc> so let's propagate it first (instead of chaining those issues or so)
<lfryc> so you are saying..
<lfryc> if serialization fails (on a proxy)..
<lfryc> then client fails and its exception is propagated instead of showing proxy's exception ?
<lfryc> aslak: ^
<lfryc> https://github.com/arquillian/arquillian-extension-warp/blob/master/impl/...
<aslak> in this case it's Client fails due to reactions to Server failure because Proxy failed on client and never arrived at server
<aslak> and i get the client failure
<aslak> it fails to create the enriched request, but the request still goes trough
<aslak> i think the actual Request should be stopped if the enrichment fails
<lfryc> ah, ic
<lfryc> yeah, that make sense
{code}
> Failure to create Enrichment hidden by Client Assertion
> -------------------------------------------------------
>
> Key: ARQ-1400
> URL: https://issues.jboss.org/browse/ARQ-1400
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Aslak Knutsen
>
> The chain of event are:
> * Activity is executed
> * Client Request fail to enrich
> * Request goes to server
> * Response comes back
> * Client asserts the Response and fail
> * Exception shown to user is the failed Client side Assertion.
> The real cause of the failure is the failed serialization of the enrichment object to setup the server side, which cause the server side response to be wrong and client assertion of course failing.
> Two things odd here:
> * Enrichment problems are hidden
> * Request still goes to server even tho we couldn't fulfill the setup
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ARQ-1400) Failure to create Enrichment hidden by Client Assertion
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-1400:
----------------------------------
Summary: Failure to create Enrichment hidden by Client Assertion
Key: ARQ-1400
URL: https://issues.jboss.org/browse/ARQ-1400
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha2
Reporter: Aslak Knutsen
The chain of event are:
* Activity is executed
* Client Request fail to enrich
* Request goes to server
* Response comes back
* Client asserts the Response and fail
* Exception shown to user is the failed Client side Assertion.
The real cause of the failure is the failed serialization of the enrichment object to setup the server side, which cause the server side response to be wrong and client assertion of course failing.
Two things odd here:
* Enrichment problems are hidden
* Request still goes to server even tho we couldn't fulfill the setup
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (ARQGRA-307) Graphhene cleanup executes even if test fails
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-307?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-307:
------------------------------
Fix Version/s: 2.0.0.Alpha5
> Graphhene cleanup executes even if test fails
> ---------------------------------------------
>
> Key: ARQGRA-307
> URL: https://issues.jboss.org/browse/ARQGRA-307
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.0.0.Alpha4
> Reporter: Michal Matloka
> Fix For: 2.0.0.Alpha5
>
>
> Example stack showing situation. Deployment failed but cleanup is executed then with an exception.
> {noformat}
> 09:33:59.562 INFO - Started org.openqa.jetty.jetty.Server@7b23d3ce
> 09:33:59.933 INFO - Reused session store is not available at /Users/someUser/.drone-webdriver-session-store, a new one will be created.
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 82.49 sec <<< FAILURE!
> com.sth.myIT Time elapsed: 82.352 sec <<< ERROR!
> java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive com.sth.myIT.createDeployment()
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:160)
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:94)
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:57)
> at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:100)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:156)
> ... 56 more
> Caused by: java.lang.NullPointerException
> at org.jboss.shrinkwrap.resolver.impl.maven.pom.ParsedPomFileImpl$FileUtils.listFiles(ParsedPomFileImpl.java:170)
> at org.jboss.shrinkwrap.resolver.impl.maven.pom.ParsedPomFileImpl.getProjectResources(ParsedPomFileImpl.java:83)
> at org.jboss.shrinkwrap.resolver.impl.maven.archive.packaging.WarPackagingProcessor.importBuildOutput(WarPackagingProcessor.java:95)
> at org.jboss.shrinkwrap.resolver.impl.maven.archive.packaging.WarPackagingProcessor.importBuildOutput(WarPackagingProcessor.java:49)
> at org.jboss.shrinkwrap.resolver.impl.maven.archive.importer.PomEquippedMavenImporterImpl.importBuildOutput(PomEquippedMavenImporterImpl.java:49)
> at org.jboss.shrinkwrap.resolver.impl.maven.archive.importer.PomEquippedMavenImporterImpl.importBuildOutput(PomEquippedMavenImporterImpl.java:44)
> at com.sth.test.ArquillianWarUtils.importBuildOutput(ArquillianWarUtils.java:28)
> at com.sth.myIT.createDeployment(myIT.java:33)
> ... 61 more
>
> com.sth.myIT Time elapsed: 82.434 sec <<< ERROR!
> java.lang.NullPointerException
> at org.jboss.arquillian.graphene.page.extension.GraphenePageExtensionRegistrar.unregisterPageExtensionRegistry(GraphenePageExtensionRegistrar.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87)
> at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
>
> 09:34:24.596 INFO - Stopping Acceptor ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=14444]
> 09:34:24.662 INFO - Stopped SocketListener on 0.0.0.0:14444
> 09:34:24.888 INFO - Stopped HttpContext[/selenium-server/driver,/selenium-server/driver]
> 09:34:24.941 INFO - Stopped HttpContext[/selenium-server,/selenium-server]
> 09:34:25.012 INFO - Stopped HttpContext[/,/]
> 09:34:25.012 INFO - Stopped org.openqa.jetty.jetty.servlet.ServletHandler@67441d86
> 09:34:25.068 INFO - Stopped HttpContext[/wd,/wd]
> 09:34:25.068 INFO - Stopped org.openqa.jetty.jetty.Server@7b23d3ce
>
> Results :
>
> Tests in error:
> com.sth.myIT: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive com.sth.myIT.createDeployment()
> com.sth.myIT
>
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years