From issues at jboss.org Fri Aug 1 08:24:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 1 Aug 2014 08:24:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1830) Only the last Test Class is reported with TestNG runner In-Reply-To: References: Message-ID: Juraj H?ska created ARQ-1830: -------------------------------- Summary: Only the last Test Class is reported with TestNG runner Key: ARQ-1830 URL: https://issues.jboss.org/browse/ARQ-1830 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: 1.0.4.Final Reporter: Juraj H?ska When you have TestNG test suite, after running only the last test class is reported. It works with JUnit nicely. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 08:26:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 1 Aug 2014 08:26:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1830) Only the last Test Class is reported with TestNG runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQ-1830: ----------------------------- Description: When you have TestNG test suite, after running, only the last test class is reported. It works with JUnit nicely. was: When you have TestNG test suite, after running only the last test class is reported. It works with JUnit nicely. > Only the last Test Class is reported with TestNG runner > ------------------------------------------------------- > > Key: ARQ-1830 > URL: https://issues.jboss.org/browse/ARQ-1830 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: 1.0.4.Final > Reporter: Juraj H?ska > > When you have TestNG test suite, after running, only the last test class is reported. > It works with JUnit nicely. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 08:38:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 1 Aug 2014 08:38:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1830) Only the last Test Class of some subset of Test classes is reported with TestNG runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQ-1830: ----------------------------- Summary: Only the last Test Class of some subset of Test classes is reported with TestNG runner (was: Only the last Test Class is reported with TestNG runner) > Only the last Test Class of some subset of Test classes is reported with TestNG runner > -------------------------------------------------------------------------------------- > > Key: ARQ-1830 > URL: https://issues.jboss.org/browse/ARQ-1830 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: 1.0.4.Final > Reporter: Juraj H?ska > > When you have TestNG test suite, after running, only the last test class is reported. > It works with JUnit nicely. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 08:40:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 1 Aug 2014 08:40:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1830) Only the last Test Class of some subset of Test classes is reported with TestNG runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQ-1830: ----------------------------- Description: When you have TestNG test suite, after running some *subset* of all test classes (particular test classes or e.g. all classes in one package), then only the last test class is reported. It works when you run all tests, and also with JUnit nicely. was: When you have TestNG test suite, after running, only the last test class is reported. It works with JUnit nicely. > Only the last Test Class of some subset of Test classes is reported with TestNG runner > -------------------------------------------------------------------------------------- > > Key: ARQ-1830 > URL: https://issues.jboss.org/browse/ARQ-1830 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: 1.0.4.Final > Reporter: Juraj H?ska > > When you have TestNG test suite, after running some *subset* of all test classes (particular test classes or e.g. all classes in one package), then only the last test class is reported. > It works when you run all tests, and also with JUnit nicely. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 08:56:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 1 Aug 2014 08:56:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1830) Only the last Test Class of some subset of Test classes is reported with TestNG runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQ-1830: ----------------------------- Affects Version/s: 1.0.0.Alpha4 (was: 1.0.4.Final) > Only the last Test Class of some subset of Test classes is reported with TestNG runner > -------------------------------------------------------------------------------------- > > Key: ARQ-1830 > URL: https://issues.jboss.org/browse/ARQ-1830 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > > When you have TestNG test suite, after running some *subset* of all test classes (particular test classes or e.g. all classes in one package), then only the last test class is reported. > It works when you run all tests, and also with JUnit nicely. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 08:56:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 1 Aug 2014 08:56:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1830) Only the last Test Class of some subset of Test classes is reported with TestNG runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQ-1830: ----------------------------- Affects Version/s: recorder_1.0.0.Alpha4 (was: 1.0.0.Alpha4) > Only the last Test Class of some subset of Test classes is reported with TestNG runner > -------------------------------------------------------------------------------------- > > Key: ARQ-1830 > URL: https://issues.jboss.org/browse/ARQ-1830 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > > When you have TestNG test suite, after running some *subset* of all test classes (particular test classes or e.g. all classes in one package), then only the last test class is reported. > It works when you run all tests, and also with JUnit nicely. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 09:00:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 1 Aug 2014 09:00:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1831) Make reported exception stack-traces more concise In-Reply-To: References: Message-ID: Juraj H?ska created ARQ-1831: -------------------------------- Summary: Make reported exception stack-traces more concise Key: ARQ-1831 URL: https://issues.jboss.org/browse/ARQ-1831 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha4 Reporter: Juraj H?ska Priority: Minor Reported exceptions stack-traces are too long, they sometimes take more then two screens. It makes report less readable. It would be nice if they are shorter. For example if they are generated to {{html}}: * then they can be written inside {{textarea}} or another block, frame with predefined height, so one will be able to scroll in such a block to reveal full stack-trace * or something like Twitter Bootstrap [collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 09:04:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 1 Aug 2014 09:04:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1831) Make reported exception stack-traces more concise In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989862#comment-12989862 ] Juraj H?ska commented on ARQ-1831: ---------------------------------- IMHO the first four-8 rows of stacktrace are usually important, it would be nice if only those lines are visible by default. Another addition I would welcome is having the exception message be bold, as for me these things are most important when looking at failed test: # name of the test method and test class # exception message # from now on screenshots as well > Make reported exception stack-traces more concise > ------------------------------------------------- > > Key: ARQ-1831 > URL: https://issues.jboss.org/browse/ARQ-1831 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Priority: Minor > > Reported exceptions stack-traces are too long, they sometimes take more then two screens. It makes report less readable. > It would be nice if they are shorter. > For example if they are generated to {{html}}: > * then they can be written inside {{textarea}} or another block, frame with predefined height, so one will be able to scroll in such a block to reveal full stack-trace > * or something like Twitter Bootstrap [collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Aug 3 03:12:29 2014 From: issues at jboss.org (Sherif Ghonaim (JIRA)) Date: Sun, 3 Aug 2014 03:12:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1832) Ticketmonster arquillian testing: Cannot deploy test.war In-Reply-To: References: Message-ID: Sherif Ghonaim created ARQ-1832: ----------------------------------- Summary: Ticketmonster arquillian testing: Cannot deploy test.war Key: ARQ-1832 URL: https://issues.jboss.org/browse/ARQ-1832 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Sherif Ghonaim -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Aug 3 03:26:33 2014 From: issues at jboss.org (Sherif Ghonaim (JIRA)) Date: Sun, 3 Aug 2014 03:26:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1832) Ticketmonster arquillian testing: Cannot deploy test.war In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sherif Ghonaim updated ARQ-1832: -------------------------------- Environment: JBoss Developer Studio Version: 7.1.1.GA Build id: GA-v20140314-2145-B688 Build date: 20140314-2145 Description: At the end of the 3rd section of the ticket monster tutorial, I got this error whenever I attempted the testing on EAP 6.1. It worked on 6.2 org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: test.war at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83) at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64) at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46) at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) 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.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) 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.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) 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.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) 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:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.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:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101) 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:84) 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:65) 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:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150) 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) Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:130) at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144) at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:101) at org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager.executeOperation(ModelControllerClientServerDeploymentManager.java:51) at org.jboss.as.controller.client.helpers.standalone.impl.AbstractServerDeploymentManager.execute(AbstractServerDeploymentManager.java:79) at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:49) at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77) ... 90 more > Ticketmonster arquillian testing: Cannot deploy test.war > -------------------------------------------------------- > > Key: ARQ-1832 > URL: https://issues.jboss.org/browse/ARQ-1832 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: JBoss Developer Studio > Version: 7.1.1.GA > Build id: GA-v20140314-2145-B688 > Build date: 20140314-2145 > Reporter: Sherif Ghonaim > > At the end of the 3rd section of the ticket monster tutorial, I got this error whenever I attempted the testing on EAP 6.1. It worked on 6.2 > org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: test.war > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83) > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64) > at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46) > at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > 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.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > 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.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > 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.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101) > 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:84) > 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:65) > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150) > 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) > Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:130) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:101) > at org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager.executeOperation(ModelControllerClientServerDeploymentManager.java:51) > at org.jboss.as.controller.client.helpers.standalone.impl.AbstractServerDeploymentManager.execute(AbstractServerDeploymentManager.java:79) > at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:49) > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77) > ... 90 more -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Aug 3 10:40:29 2014 From: issues at jboss.org (Jakub Narloch (JIRA)) Date: Sun, 3 Aug 2014 10:40:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1833) Spring Boot Integration In-Reply-To: References: Message-ID: Jakub Narloch created ARQ-1833: ---------------------------------- Summary: Spring Boot Integration Key: ARQ-1833 URL: https://issues.jboss.org/browse/ARQ-1833 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Spring Affects Versions: spring_1.0.0.Beta3 Reporter: Jakub Narloch Assignee: Jakub Narloch Spring Boot is the new hot feature in the Spring world allowing to configure/setup application based on the classpath scaning depedencies or extension, quite similary how the Arquillian load it's extensions. We could add such support through enable to configure the application context through the SpringApplication similary as the SpringApplicationConfiguration does and by creating spring-boot-arquilian-starter module that would set up proper depedencies in the classpath. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Aug 3 11:44:29 2014 From: issues at jboss.org (Jakub Narloch (JIRA)) Date: Sun, 3 Aug 2014 11:44:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1834) Spring extension - Optional/Conditional feature loading In-Reply-To: References: Message-ID: Jakub Narloch created ARQ-1834: ---------------------------------- Summary: Spring extension - Optional/Conditional feature loading Key: ARQ-1834 URL: https://issues.jboss.org/browse/ARQ-1834 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jakub Narloch Spring Boot gives my the idea on how to workaround the problem that Arquillian is versioned completly seperatly from the Spring Framework. Causing problems when trying to target functionality from specific Spring version. At the moment this has been handled by providing many artifacts each with support for different Spring version. But I wonder whether this could not be done a bit smarter with a form of dynamic recognition what is actually avaible on the classpath and in the same time enabling proper extension and or version for which this is targeted. Either way this would be rather a task for next major Spring extension version, becouse most likely this would break the backward compatibility and would probably will mean that we may change the organization of the extension artifacts. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Aug 3 13:04:29 2014 From: issues at jboss.org (Jakub Narloch (JIRA)) Date: Sun, 3 Aug 2014 13:04:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1834) Spring extension - Optional/Conditional feature loading In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Narloch updated ARQ-1834: ------------------------------- Component/s: Extension - Spring > Spring extension - Optional/Conditional feature loading > ------------------------------------------------------- > > Key: ARQ-1834 > URL: https://issues.jboss.org/browse/ARQ-1834 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spring > Reporter: Jakub Narloch > > Spring Boot gives my the idea on how to workaround the problem that Arquillian is versioned completly seperatly from the Spring Framework. Causing problems when trying to target functionality from specific Spring version. At the moment this has been handled by providing many artifacts each with support for different Spring version. But I wonder whether this could not be done a bit smarter with a form of dynamic recognition what is actually avaible on the classpath and in the same time enabling proper extension and or version for which this is targeted. > Either way this would be rather a task for next major Spring extension version, becouse most likely this would break the backward compatibility and would probably will mean that we may change the organization of the extension artifacts. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Aug 3 13:16:33 2014 From: issues at jboss.org (Jakub Narloch (JIRA)) Date: Sun, 3 Aug 2014 13:16:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1834) Spring extension - Optional/Conditional feature loading In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Narloch reassigned ARQ-1834: ---------------------------------- Assignee: Jakub Narloch > Spring extension - Optional/Conditional feature loading > ------------------------------------------------------- > > Key: ARQ-1834 > URL: https://issues.jboss.org/browse/ARQ-1834 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spring > Reporter: Jakub Narloch > Assignee: Jakub Narloch > > Spring Boot gives my the idea on how to workaround the problem that Arquillian is versioned completly seperatly from the Spring Framework. Causing problems when trying to target functionality from specific Spring version. At the moment this has been handled by providing many artifacts each with support for different Spring version. But I wonder whether this could not be done a bit smarter with a form of dynamic recognition what is actually avaible on the classpath and in the same time enabling proper extension and or version for which this is targeted. > Either way this would be rather a task for next major Spring extension version, becouse most likely this would break the backward compatibility and would probably will mean that we may change the organization of the extension artifacts. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 06:00:43 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 4 Aug 2014 06:00:43 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1797) Allow screenshooter configuration to be locally overridden In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1797: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha4 > Allow screenshooter configuration to be locally overridden > ----------------------------------------------------------- > > Key: ARQ-1797 > URL: https://issues.jboss.org/browse/ARQ-1797 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Jakub Cechacek > Assignee: Stefan Miklosovic > Priority: Optional > Fix For: recorder_1.0.0.Alpha4 > > > Currently the configuration of Screenshooter is done globally inside arquillian.xml. It would be useful to provide a way how to change this configuration locally for specific class. > Example: > arquillian xml: > {code} > false > false > false > true > {code} > This configuration is sufficient for the majority of my tests. However then there are those few complicated / unstable tests for which I would like to take more screenshots. AFAIK there is no way how to change the configuration only for these tests. > Nice solution would be to provide an annotation which will allow you to change the configuration. Something like > {code} > @Screenshot(onEveryAction=true, afterTest=True, beforeTest=True) > public class MyUnstableTestCase() > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 06:00:44 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 4 Aug 2014 06:00:44 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1797) Allow screenshooter configuration to be locally overridden In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1797. ------------------------------------ Resolution: Done > Allow screenshooter configuration to be locally overridden > ----------------------------------------------------------- > > Key: ARQ-1797 > URL: https://issues.jboss.org/browse/ARQ-1797 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Jakub Cechacek > Assignee: Stefan Miklosovic > Priority: Optional > Fix For: recorder_1.0.0.Alpha4 > > > Currently the configuration of Screenshooter is done globally inside arquillian.xml. It would be useful to provide a way how to change this configuration locally for specific class. > Example: > arquillian xml: > {code} > false > false > false > true > {code} > This configuration is sufficient for the majority of my tests. However then there are those few complicated / unstable tests for which I would like to take more screenshots. AFAIK there is no way how to change the configuration only for these tests. > Nice solution would be to provide an annotation which will allow you to change the configuration. Something like > {code} > @Screenshot(onEveryAction=true, afterTest=True, beforeTest=True) > public class MyUnstableTestCase() > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 06:12:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 4 Aug 2014 06:12:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1831) Make reported exception stack-traces more concise In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990103#comment-12990103 ] Stefan Miklosovic commented on ARQ-1831: ---------------------------------------- Making exception message bold is trivial. Your PR are welcome. I do not like depending on anything else but html, css a maybe some basic java script / jquery. I do not like to depend on any external lib. > Make reported exception stack-traces more concise > ------------------------------------------------- > > Key: ARQ-1831 > URL: https://issues.jboss.org/browse/ARQ-1831 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Priority: Minor > > Reported exceptions stack-traces are too long, they sometimes take more then two screens. It makes report less readable. > It would be nice if they are shorter. > For example if they are generated to {{html}}: > * then they can be written inside {{textarea}} or another block, frame with predefined height, so one will be able to scroll in such a block to reveal full stack-trace > * or something like Twitter Bootstrap [collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 16:22:30 2014 From: issues at jboss.org (Juergen Zimmermann (JIRA)) Date: Mon, 4 Aug 2014 16:22:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1835) JUnit 4.12-beta-1 results in UnsupportedOperationException In-Reply-To: References: Message-ID: Juergen Zimmermann created ARQ-1835: --------------------------------------- Summary: JUnit 4.12-beta-1 results in UnsupportedOperationException Key: ARQ-1835 URL: https://issues.jboss.org/browse/ARQ-1835 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.5.Final Reporter: Juergen Zimmermann When I configure my pom.xml so that JUnit 4.12-beta-1 is used than an UnsupportedOperationException is thrown: {code} java.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableList$1.set(Collections.java:1412) at java.util.Collections.sort(Collections.java:234) at org.jboss.arquillian.junit.Arquillian.getChildren(Arquillian.java:73) at org.junit.runners.ParentRunner.getFilteredChildren(ParentRunner.java:426) at org.junit.runners.ParentRunner.getDescription(ParentRunner.java:351) at org.junit.runners.ParentRunner.run(ParentRunner.java:359) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 04:02:29 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 5 Aug 2014 04:02:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1836) Support HtmlUnitDriver client options In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1836: -------------------------------- Summary: Support HtmlUnitDriver client options Key: ARQ-1836 URL: https://issues.jboss.org/browse/ARQ-1836 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_2.0.0.Alpha2 Reporter: Karel Piwko There are options that could be set for HtmlUnitDriver but are not available in Drone configuration. Drone would need to proxy HtmlUnitDriver and override protected {{modifyWebClient}} method because this is not exposed in Selenium. https://code.google.com/p/selenium/source/browse/java/client/src/org/openqa/selenium/htmlunit/HtmlUnitDriver.java?r=1615e198f0e0b9d7a0cc60bedf475fe23b9c7e1e#266 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 04:20:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 5 Aug 2014 04:20:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1829) Reporting ScreenshotEntry with phase == onEveryAction is not possible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1829: ----------------------------------- Affects Version/s: recorder_1.0.0.Alpha4 (was: 1.0.0.Alpha4) > Reporting ScreenshotEntry with phase == onEveryAction is not possible > --------------------------------------------------------------------- > > Key: ARQ-1829 > URL: https://issues.jboss.org/browse/ARQ-1829 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > When I have: > {code} > ScreenshotEntry propertyEntry = new ScreenshotEntry(); > propertyEntry.setPhase(When.ON_EVERY_ACTION); > ... > propertyReportEvent.fire(new PropertyReportEvent(propertyEntry)); > {code} > then such a screenshot is not part of the generated report. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 04:22:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 5 Aug 2014 04:22:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1710) Integrate desktop video recorder project to recorder extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1710: ----------------------------------- Fix Version/s: (was: recorder_1.0.0.Alpha4) > Integrate desktop video recorder project to recorder extension > -------------------------------------------------------------- > > Key: ARQ-1710 > URL: https://issues.jboss.org/browse/ARQ-1710 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 04:22:30 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 5 Aug 2014 04:22:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1710) Integrate desktop video recorder project to recorder extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1710. ---------------------------------- > Integrate desktop video recorder project to recorder extension > -------------------------------------------------------------- > > Key: ARQ-1710 > URL: https://issues.jboss.org/browse/ARQ-1710 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 04:24:30 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 5 Aug 2014 04:24:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1679) When expected exception is thrown in test method, reporter should not report it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1679. ---------------------------------- > When expected exception is thrown in test method, reporter should not report it > ------------------------------------------------------------------------------- > > Key: ARQ-1679 > URL: https://issues.jboss.org/browse/ARQ-1679 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha4 > > > When I have > {code} > @Test(expected = SomeException.class) > public void someTest() { > throw new SomeException("this is test exception"); > } > {code} > It should not appear in resulting report. Take JUnit @Rule into account as well. > Take into consideration various test frameworks. > https://github.com/arquillian/arquillian-recorder/blob/1.0.0.Alpha1/arquillian-recorder-reporter/arquillian-recorder-reporter-impl/src/main/java/org/arquillian/recorder/reporter/impl/ReporterLifecycleObserver.java#L164-L168 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 04:24:31 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 5 Aug 2014 04:24:31 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1716) Provide support for TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1716. ---------------------------------- > Provide support for TestNG > -------------------------- > > Key: ARQ-1716 > URL: https://issues.jboss.org/browse/ARQ-1716 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: recorder_1.0.0.Alpha4 > > > Reporter extension does not work properly with TestNG. For example when test fails with exception, it causes to throw exception by reporter as well: > {code} > arquillianAfterTest(org.richfaces.tests.showcase.ajax.TestAjax) Time elapsed: 5.797 sec <<< FAILURE! > java.lang.IllegalStateException: Test method is not annotated with @Test annotation > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.isThrowingExpectedException(ReporterLifecycleObserver.java:262) > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.observeAfterTest(ReporterLifecycleObserver.java:178) > 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:606) > 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:606) > 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:606) > 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:102) > 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:606) > 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:84) > 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:606) > 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:65) > 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:606) > 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.testng.Arquillian.arquillianAfterTest(Arquillian.java:149) > 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:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:753) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1178) > at org.testng.TestRunner.privateRun(TestRunner.java:757) > at org.testng.TestRunner.run(TestRunner.java:608) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) > at org.testng.TestNG.run(TestNG.java:999) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:69) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:120) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:104) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} > Its because it is tested only for {{@Test}} from junit package. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 04:24:31 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 5 Aug 2014 04:24:31 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1701. ---------------------------------- > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha4 > > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 04:24:31 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 5 Aug 2014 04:24:31 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1740. ---------------------------------- > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha4 > > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 04:24:32 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 5 Aug 2014 04:24:32 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1797) Allow screenshooter configuration to be locally overridden In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1797. ---------------------------------- > Allow screenshooter configuration to be locally overridden > ----------------------------------------------------------- > > Key: ARQ-1797 > URL: https://issues.jboss.org/browse/ARQ-1797 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Jakub Cechacek > Assignee: Stefan Miklosovic > Priority: Optional > Fix For: recorder_1.0.0.Alpha4 > > > Currently the configuration of Screenshooter is done globally inside arquillian.xml. It would be useful to provide a way how to change this configuration locally for specific class. > Example: > arquillian xml: > {code} > false > false > false > true > {code} > This configuration is sufficient for the majority of my tests. However then there are those few complicated / unstable tests for which I would like to take more screenshots. AFAIK there is no way how to change the configuration only for these tests. > Nice solution would be to provide an annotation which will allow you to change the configuration. Something like > {code} > @Screenshot(onEveryAction=true, afterTest=True, beforeTest=True) > public class MyUnstableTestCase() > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 05:58:30 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 5 Aug 2014 05:58:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1837) Implement exporter which feeds database with test report In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1837: -------------------------------------- Summary: Implement exporter which feeds database with test report Key: ARQ-1837 URL: https://issues.jboss.org/browse/ARQ-1837 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha4 Reporter: Stefan Miklosovic It could be e.g. sqlite or propper db, using jdbc underneath. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 06:58:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 5 Aug 2014 06:58:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1837) Implement exporter which feeds database with test report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1837: ----------------------------------- Priority: Optional (was: Major) > Implement exporter which feeds database with test report > -------------------------------------------------------- > > Key: ARQ-1837 > URL: https://issues.jboss.org/browse/ARQ-1837 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Priority: Optional > > It could be e.g. sqlite or propper db, using jdbc underneath. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 13:32:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 5 Aug 2014 13:32:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1829) Reporting ScreenshotEntry with phase == onEveryAction is not possible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQ-1829: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-recorder/pull/7 > Reporting ScreenshotEntry with phase == onEveryAction is not possible > --------------------------------------------------------------------- > > Key: ARQ-1829 > URL: https://issues.jboss.org/browse/ARQ-1829 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > When I have: > {code} > ScreenshotEntry propertyEntry = new ScreenshotEntry(); > propertyEntry.setPhase(When.ON_EVERY_ACTION); > ... > propertyReportEvent.fire(new PropertyReportEvent(propertyEntry)); > {code} > then such a screenshot is not part of the generated report. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 13:36:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 5 Aug 2014 13:36:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1829) Reporting ScreenshotEntry with phase == onEveryAction is not possible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990523#comment-12990523 ] Juraj H?ska commented on ARQ-1829: ---------------------------------- I have linked PR which should resolve this issue. > Reporting ScreenshotEntry with phase == onEveryAction is not possible > --------------------------------------------------------------------- > > Key: ARQ-1829 > URL: https://issues.jboss.org/browse/ARQ-1829 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > When I have: > {code} > ScreenshotEntry propertyEntry = new ScreenshotEntry(); > propertyEntry.setPhase(When.ON_EVERY_ACTION); > ... > propertyReportEvent.fire(new PropertyReportEvent(propertyEntry)); > {code} > then such a screenshot is not part of the generated report. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 13:38:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 5 Aug 2014 13:38:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-456) Screenshots made onEveryAction are reported as screenshots made onBefore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-456: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-recorder/pull/7 > Screenshots made onEveryAction are reported as screenshots made onBefore > ------------------------------------------------------------------------ > > Key: ARQGRA-456 > URL: https://issues.jboss.org/browse/ARQGRA-456 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: 2.1.0.Alpha2 > > Attachments: wrongOnEveryAction.png > > > The problem is that {{TakeScreenshotEvent}} is always fired only with {{onBefore}}. > I need to change this phase when appropriate for {{onEveryAction}}. > Possible candidates: > * before injecting into interceptors, [here|https://github.com/arquillian/arquillian-graphene/blob/2.1.x/extension/screenshooter/src/main/java/org/arquillian/extension/recorder/screenshooter/browser/impl/ScreenshotTaker.java#L67] > * in the interceptor itself, somewhere inside this [block|https://github.com/arquillian/arquillian-graphene/blob/2.1.x/extension/screenshooter/src/main/java/org/arquillian/extension/recorder/screenshooter/browser/impl/TakeScreenshotOnEveryActionInterceptor.java#L60]. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 13:38:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 5 Aug 2014 13:38:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-456) Screenshots made onEveryAction are reported as screenshots made onBefore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990524#comment-12990524 ] Juraj H?ska commented on ARQGRA-456: ------------------------------------ Linked PR with fix, it should be merge just after the PR in linked upstream issue is merged. > Screenshots made onEveryAction are reported as screenshots made onBefore > ------------------------------------------------------------------------ > > Key: ARQGRA-456 > URL: https://issues.jboss.org/browse/ARQGRA-456 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: 2.1.0.Alpha2 > > Attachments: wrongOnEveryAction.png > > > The problem is that {{TakeScreenshotEvent}} is always fired only with {{onBefore}}. > I need to change this phase when appropriate for {{onEveryAction}}. > Possible candidates: > * before injecting into interceptors, [here|https://github.com/arquillian/arquillian-graphene/blob/2.1.x/extension/screenshooter/src/main/java/org/arquillian/extension/recorder/screenshooter/browser/impl/ScreenshotTaker.java#L67] > * in the interceptor itself, somewhere inside this [block|https://github.com/arquillian/arquillian-graphene/blob/2.1.x/extension/screenshooter/src/main/java/org/arquillian/extension/recorder/screenshooter/browser/impl/TakeScreenshotOnEveryActionInterceptor.java#L60]. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 04:24:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 6 Aug 2014 04:24:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-456) Screenshots made onEveryAction are reported as screenshots made onBefore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQGRA-456: ------------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/118 (was: https://github.com/arquillian/arquillian-recorder/pull/7) > Screenshots made onEveryAction are reported as screenshots made onBefore > ------------------------------------------------------------------------ > > Key: ARQGRA-456 > URL: https://issues.jboss.org/browse/ARQGRA-456 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: 2.1.0.Alpha2 > > Attachments: wrongOnEveryAction.png > > > The problem is that {{TakeScreenshotEvent}} is always fired only with {{onBefore}}. > I need to change this phase when appropriate for {{onEveryAction}}. > Possible candidates: > * before injecting into interceptors, [here|https://github.com/arquillian/arquillian-graphene/blob/2.1.x/extension/screenshooter/src/main/java/org/arquillian/extension/recorder/screenshooter/browser/impl/ScreenshotTaker.java#L67] > * in the interceptor itself, somewhere inside this [block|https://github.com/arquillian/arquillian-graphene/blob/2.1.x/extension/screenshooter/src/main/java/org/arquillian/extension/recorder/screenshooter/browser/impl/TakeScreenshotOnEveryActionInterceptor.java#L60]. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 04:28:30 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 6 Aug 2014 04:28:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1829) Reporting ScreenshotEntry with phase == onEveryAction is not possible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1829: ----------------------------------- Fix Version/s: recorder_1.0.0.Beta1 > Reporting ScreenshotEntry with phase == onEveryAction is not possible > --------------------------------------------------------------------- > > Key: ARQ-1829 > URL: https://issues.jboss.org/browse/ARQ-1829 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: recorder_1.0.0.Beta1 > > > When I have: > {code} > ScreenshotEntry propertyEntry = new ScreenshotEntry(); > propertyEntry.setPhase(When.ON_EVERY_ACTION); > ... > propertyReportEvent.fire(new PropertyReportEvent(propertyEntry)); > {code} > then such a screenshot is not part of the generated report. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 04:28:30 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 6 Aug 2014 04:28:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1829) Reporting ScreenshotEntry with phase == onEveryAction is not possible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1829: ----------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done > Reporting ScreenshotEntry with phase == onEveryAction is not possible > --------------------------------------------------------------------- > > Key: ARQ-1829 > URL: https://issues.jboss.org/browse/ARQ-1829 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: recorder_1.0.0.Beta1 > > > When I have: > {code} > ScreenshotEntry propertyEntry = new ScreenshotEntry(); > propertyEntry.setPhase(When.ON_EVERY_ACTION); > ... > propertyReportEvent.fire(new PropertyReportEvent(propertyEntry)); > {code} > then such a screenshot is not part of the generated report. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 05:12:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 6 Aug 2014 05:12:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1838) Add message to taken screenshot and video for documentation purposes In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1838: -------------------------------------- Summary: Add message to taken screenshot and video for documentation purposes Key: ARQ-1838 URL: https://issues.jboss.org/browse/ARQ-1838 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha4 Reporter: Stefan Miklosovic https://github.com/arquillian/arquillian-recorder/issues/6 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 07:54:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 6 Aug 2014 07:54:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1831) Make reported exception stack-traces more concise In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska reassigned ARQ-1831: -------------------------------- Assignee: Juraj H?ska > Make reported exception stack-traces more concise > ------------------------------------------------- > > Key: ARQ-1831 > URL: https://issues.jboss.org/browse/ARQ-1831 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Minor > > Reported exceptions stack-traces are too long, they sometimes take more then two screens. It makes report less readable. > It would be nice if they are shorter. > For example if they are generated to {{html}}: > * then they can be written inside {{textarea}} or another block, frame with predefined height, so one will be able to scroll in such a block to reveal full stack-trace > * or something like Twitter Bootstrap [collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 10:44:30 2014 From: issues at jboss.org (=?UTF-8?Q?Oliver_Ki=C5=A1=C5=A1_=28JIRA=29?=) Date: Wed, 6 Aug 2014 10:44:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-455) Guarded XHR2 request fails when its onload callback is JQuery proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Ki?? reassigned ARQGRA-455: ---------------------------------- Assignee: Oliver Ki?? > Guarded XHR2 request fails when its onload callback is JQuery proxy > ------------------------------------------------------------------- > > Key: ARQGRA-455 > URL: https://issues.jboss.org/browse/ARQGRA-455 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juraj H?ska > Assignee: Oliver Ki?? > > If Graphene is guarding an AJAX request, which {{onload}} callback is JQUery proxy, then it fails. There is a problem with arguments passing. > *XHR2 request*: > {code:javascript} > function makeXHR2() { > var xhr = new XMLHttpRequest(); > xhr.open("GET", "sample1.html", true); > xhr.responseType = 'text'; > > xhr.onload = $.proxy(function (e) { > switch (e.target.status) { > case 200: > console.log('HTTP 200'); > break; > default: > console.log('HTTP 500'); > } > > var responseContext = { > } > }, this); > > xhr.send(null); > } > {code} > In browser console there is an error that states: > {code} > e.target is undefined > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 10:44:30 2014 From: issues at jboss.org (=?UTF-8?Q?Oliver_Ki=C5=A1=C5=A1_=28JIRA=29?=) Date: Wed, 6 Aug 2014 10:44:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-455) Guarded XHR2 request fails when its onload callback is JQuery proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Ki?? updated ARQGRA-455: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/119 > Guarded XHR2 request fails when its onload callback is JQuery proxy > ------------------------------------------------------------------- > > Key: ARQGRA-455 > URL: https://issues.jboss.org/browse/ARQGRA-455 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juraj H?ska > Assignee: Oliver Ki?? > > If Graphene is guarding an AJAX request, which {{onload}} callback is JQUery proxy, then it fails. There is a problem with arguments passing. > *XHR2 request*: > {code:javascript} > function makeXHR2() { > var xhr = new XMLHttpRequest(); > xhr.open("GET", "sample1.html", true); > xhr.responseType = 'text'; > > xhr.onload = $.proxy(function (e) { > switch (e.target.status) { > case 200: > console.log('HTTP 200'); > break; > default: > console.log('HTTP 500'); > } > > var responseContext = { > } > }, this); > > xhr.send(null); > } > {code} > In browser console there is an error that states: > {code} > e.target is undefined > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 10:50:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 6 Aug 2014 10:50:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-456) Screenshots made onEveryAction are reported as screenshots made onBefore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-456: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Screenshots made onEveryAction are reported as screenshots made onBefore > ------------------------------------------------------------------------ > > Key: ARQGRA-456 > URL: https://issues.jboss.org/browse/ARQGRA-456 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: 2.1.0.Alpha2 > > Attachments: wrongOnEveryAction.png > > > The problem is that {{TakeScreenshotEvent}} is always fired only with {{onBefore}}. > I need to change this phase when appropriate for {{onEveryAction}}. > Possible candidates: > * before injecting into interceptors, [here|https://github.com/arquillian/arquillian-graphene/blob/2.1.x/extension/screenshooter/src/main/java/org/arquillian/extension/recorder/screenshooter/browser/impl/ScreenshotTaker.java#L67] > * in the interceptor itself, somewhere inside this [block|https://github.com/arquillian/arquillian-graphene/blob/2.1.x/extension/screenshooter/src/main/java/org/arquillian/extension/recorder/screenshooter/browser/impl/TakeScreenshotOnEveryActionInterceptor.java#L60]. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 10:50:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 6 Aug 2014 10:50:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-456) Screenshots made onEveryAction are reported as screenshots made onBefore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed ARQGRA-456. ------------------------------ Verified. Closing. > Screenshots made onEveryAction are reported as screenshots made onBefore > ------------------------------------------------------------------------ > > Key: ARQGRA-456 > URL: https://issues.jboss.org/browse/ARQGRA-456 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: 2.1.0.Alpha2 > > Attachments: wrongOnEveryAction.png > > > The problem is that {{TakeScreenshotEvent}} is always fired only with {{onBefore}}. > I need to change this phase when appropriate for {{onEveryAction}}. > Possible candidates: > * before injecting into interceptors, [here|https://github.com/arquillian/arquillian-graphene/blob/2.1.x/extension/screenshooter/src/main/java/org/arquillian/extension/recorder/screenshooter/browser/impl/ScreenshotTaker.java#L67] > * in the interceptor itself, somewhere inside this [block|https://github.com/arquillian/arquillian-graphene/blob/2.1.x/extension/screenshooter/src/main/java/org/arquillian/extension/recorder/screenshooter/browser/impl/TakeScreenshotOnEveryActionInterceptor.java#L60]. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 12:02:32 2014 From: issues at jboss.org (Vasil Svetoslavov (JIRA)) Date: Wed, 6 Aug 2014 12:02:32 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-814) Should support injection of EJBs (as CDI Beans) in Weld Embedded In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990845#comment-12990845 ] Vasil Svetoslavov commented on ARQ-814: --------------------------------------- Any chance of this issue getting any progress? > Should support injection of EJBs (as CDI Beans) in Weld Embedded > ---------------------------------------------------------------- > > Key: ARQ-814 > URL: https://issues.jboss.org/browse/ARQ-814 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR3 > Reporter: Anthony O. > Assignee: Marko Luk?a > Attachments: EJBTest.java > > > As seen in [this post on the Arquillian forum|https://community.jboss.org/message/723563], we cannot test that simple class as an NPE is thrown from {{org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.MockEjBServices}} which seems to be a copy of Weld code as [Aslak Knutsen|https://community.jboss.org/people/aslak] said. > {code} > @RunWith(Arquillian.class) > public class EJBTest { > @Deployment > public static JavaArchive createTestArchive() { > return ShrinkWrap > .create(JavaArchive.class, "test.jar") > .addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); > } > @Stateless > public static class SomeService { > public String someMethod() { > return "test"; > } > } > @Inject > SomeService someService; > @Test > public void testStatelessCall() { > Assert.assertEquals("test", someService.someMethod()); > } > } > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 15:22:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 6 Aug 2014 15:22:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1838) Add message to taken screenshot and video for documentation purposes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1838: -------------------------------------- Assignee: Stefan Miklosovic > Add message to taken screenshot and video for documentation purposes > -------------------------------------------------------------------- > > Key: ARQ-1838 > URL: https://issues.jboss.org/browse/ARQ-1838 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > https://github.com/arquillian/arquillian-recorder/issues/6 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 15:22:30 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 6 Aug 2014 15:22:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1838) Add message to taken screenshot and video for documentation purposes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-1838 started by Stefan Miklosovic. > Add message to taken screenshot and video for documentation purposes > -------------------------------------------------------------------- > > Key: ARQ-1838 > URL: https://issues.jboss.org/browse/ARQ-1838 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > https://github.com/arquillian/arquillian-recorder/issues/6 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 18:44:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 6 Aug 2014 18:44:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1838) Add message to taken screenshot and video for documentation purposes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-1838 stopped by Stefan Miklosovic. > Add message to taken screenshot and video for documentation purposes > -------------------------------------------------------------------- > > Key: ARQ-1838 > URL: https://issues.jboss.org/browse/ARQ-1838 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > https://github.com/arquillian/arquillian-recorder/issues/6 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 18:46:31 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 6 Aug 2014 18:46:31 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1838) Add message to taken screenshot and video for documentation purposes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1838. ------------------------------------ Fix Version/s: recorder_1.0.0.Beta1 Resolution: Done https://github.com/arquillian/arquillian-recorder/commit/7c16da1734359e05effd5632c15468a430448e2d {code} @ArquillianResource private Screenshooter screenshooter; public void test() { screenshooter.setMessage("this is awesome image").takeScreenshot(); } {code} that message will appear in resulting report logically paired with taken screenshot > Add message to taken screenshot and video for documentation purposes > -------------------------------------------------------------------- > > Key: ARQ-1838 > URL: https://issues.jboss.org/browse/ARQ-1838 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Beta1 > > > https://github.com/arquillian/arquillian-recorder/issues/6 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 18:54:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 6 Aug 2014 18:54:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1824) Support Google Inc.:Google APIs (x86 System Image):19 format In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1824. ------------------------------------ Assignee: Karel Piwko Fix Version/s: droidium_1.0.0.Beta1 Resolution: Done https://github.com/arquillian/arquillian-droidium/commit/6571819b9f0c88ea1ca0ad4136f2c8348ae0afdc > Support Google Inc.:Google APIs (x86 System Image):19 format > ------------------------------------------------------------ > > Key: ARQ-1824 > URL: https://issues.jboss.org/browse/ARQ-1824 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha5 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: droidium_1.0.0.Beta1 > > > With new version format in Android SDK, we need to alter parsing options to support '()' in target format. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 02:18:30 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 7 Aug 2014 02:18:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-455) Guarded XHR2 request fails when its onload callback is JQuery proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-455: ------------------------------ Fix Version/s: 2.0.4.Final > Guarded XHR2 request fails when its onload callback is JQuery proxy > ------------------------------------------------------------------- > > Key: ARQGRA-455 > URL: https://issues.jboss.org/browse/ARQGRA-455 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juraj H?ska > Assignee: Oliver Ki?? > Fix For: 2.0.4.Final > > > If Graphene is guarding an AJAX request, which {{onload}} callback is JQUery proxy, then it fails. There is a problem with arguments passing. > *XHR2 request*: > {code:javascript} > function makeXHR2() { > var xhr = new XMLHttpRequest(); > xhr.open("GET", "sample1.html", true); > xhr.responseType = 'text'; > > xhr.onload = $.proxy(function (e) { > switch (e.target.status) { > case 200: > console.log('HTTP 200'); > break; > default: > console.log('HTTP 500'); > } > > var responseContext = { > } > }, this); > > xhr.send(null); > } > {code} > In browser console there is an error that states: > {code} > e.target is undefined > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 02:18:30 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 7 Aug 2014 02:18:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-455) Guarded XHR2 request fails when its onload callback is JQuery proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-455: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Guarded XHR2 request fails when its onload callback is JQuery proxy > ------------------------------------------------------------------- > > Key: ARQGRA-455 > URL: https://issues.jboss.org/browse/ARQGRA-455 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juraj H?ska > Assignee: Oliver Ki?? > Fix For: 2.0.4.Final > > > If Graphene is guarding an AJAX request, which {{onload}} callback is JQUery proxy, then it fails. There is a problem with arguments passing. > *XHR2 request*: > {code:javascript} > function makeXHR2() { > var xhr = new XMLHttpRequest(); > xhr.open("GET", "sample1.html", true); > xhr.responseType = 'text'; > > xhr.onload = $.proxy(function (e) { > switch (e.target.status) { > case 200: > console.log('HTTP 200'); > break; > default: > console.log('HTTP 500'); > } > > var responseContext = { > } > }, this); > > xhr.send(null); > } > {code} > In browser console there is an error that states: > {code} > e.target is undefined > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 05:22:34 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 7 Aug 2014 05:22:34 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-455) Guarded XHR2 request fails when its onload callback is JQuery proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991158#comment-12991158 ] Juraj H?ska commented on ARQGRA-455: ------------------------------------ Thanks [~okiss], it resolved also the problems with fileUpload testing. > Guarded XHR2 request fails when its onload callback is JQuery proxy > ------------------------------------------------------------------- > > Key: ARQGRA-455 > URL: https://issues.jboss.org/browse/ARQGRA-455 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juraj H?ska > Assignee: Oliver Ki?? > Fix For: 2.0.4.Final > > > If Graphene is guarding an AJAX request, which {{onload}} callback is JQUery proxy, then it fails. There is a problem with arguments passing. > *XHR2 request*: > {code:javascript} > function makeXHR2() { > var xhr = new XMLHttpRequest(); > xhr.open("GET", "sample1.html", true); > xhr.responseType = 'text'; > > xhr.onload = $.proxy(function (e) { > switch (e.target.status) { > case 200: > console.log('HTTP 200'); > break; > default: > console.log('HTTP 500'); > } > > var responseContext = { > } > }, this); > > xhr.send(null); > } > {code} > In browser console there is an error that states: > {code} > e.target is undefined > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 11:06:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 7 Aug 2014 11:06:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1839) Reporter: if test does not have screenshots then next test report has wrong indentation In-Reply-To: References: Message-ID: Juraj H?ska created ARQ-1839: -------------------------------- Summary: Reporter: if test does not have screenshots then next test report has wrong indentation Key: ARQ-1839 URL: https://issues.jboss.org/browse/ARQ-1839 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha4 Reporter: Juraj H?ska Priority: Trivial Attachments: wrongIndentation.png Please see screenshot for more information what I mean. There is probably some small CSS issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 11:06:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 7 Aug 2014 11:06:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1839) Reporter: if test does not have screenshots then next test report has wrong indentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQ-1839: ----------------------------- Attachment: wrongIndentation.png > Reporter: if test does not have screenshots then next test report has wrong indentation > --------------------------------------------------------------------------------------- > > Key: ARQ-1839 > URL: https://issues.jboss.org/browse/ARQ-1839 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Priority: Trivial > Attachments: wrongIndentation.png > > > Please see screenshot for more information what I mean. > There is probably some small CSS issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 15:12:30 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 7 Aug 2014 15:12:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1840) Add syntax highlight to Stacktraces in Report In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1840: ---------------------------------- Summary: Add syntax highlight to Stacktraces in Report Key: ARQ-1840 URL: https://issues.jboss.org/browse/ARQ-1840 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha4 Reporter: Aslak Knutsen -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 11 04:38:31 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 11 Aug 2014 04:38:31 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991918#comment-12991918 ] Luk?? Fry? commented on ARQGRA-446: ----------------------------------- Hey Chris, your fix is now available in {{2.1.0.Alpha1}}: http://arquillian.org/blog/2014/08/07/arquillian-graphene-2-1-0-Alpha1/ > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Assignee: Chris Jones > Fix For: 2.1.0.Alpha1 > > Attachments: graphene-groovy-test.zip, groovy-page-support (fixed paths).patch, groovy-page-support.patch > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 11 08:30:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 11 Aug 2014 08:30:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1839) Reporter: if test does not have screenshots then next test report has wrong indentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska reassigned ARQ-1839: -------------------------------- Assignee: Juraj H?ska > Reporter: if test does not have screenshots then next test report has wrong indentation > --------------------------------------------------------------------------------------- > > Key: ARQ-1839 > URL: https://issues.jboss.org/browse/ARQ-1839 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Trivial > Attachments: wrongIndentation.png > > > Please see screenshot for more information what I mean. > There is probably some small CSS issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 11 08:30:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 11 Aug 2014 08:30:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1830) Only the last Test Class of some subset of Test classes is reported with TestNG runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991977#comment-12991977 ] Juraj H?ska commented on ARQ-1830: ---------------------------------- [~smikloso] could you please give me some entry points, the places in the code where this issue is likely to be introduced ? > Only the last Test Class of some subset of Test classes is reported with TestNG runner > -------------------------------------------------------------------------------------- > > Key: ARQ-1830 > URL: https://issues.jboss.org/browse/ARQ-1830 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > > When you have TestNG test suite, after running some *subset* of all test classes (particular test classes or e.g. all classes in one package), then only the last test class is reported. > It works when you run all tests, and also with JUnit nicely. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 11 08:42:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 11 Aug 2014 08:42:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991978#comment-12991978 ] Stefan Miklosovic commented on ARQ-1728: ---------------------------------------- I tried to implement this as described above some weeks ago but it was just too complicated to do. I wanted to implement some tailing of that log file and parse it but when you run it in a thread, reading was blocking operation it I was not able to kill that thread then because it was not interruptible. So that nio stuff was another option which is able to do this but it gave it up in the middle. This approach is way to go, HTH > Add possibility to report AS console output related to test methods > ------------------------------------------------------------------- > > Key: ARQ-1728 > URL: https://issues.jboss.org/browse/ARQ-1728 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > > There is not any possiblity to see what AS has written out to console with test methods. > Investigate a way how to match output from AS with particular test method during which that console output has occured. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 11 08:44:30 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 11 Aug 2014 08:44:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991978#comment-12991978 ] Stefan Miklosovic edited comment on ARQ-1728 at 8/11/14 8:42 AM: ----------------------------------------------------------------- I tried to implement this as described above some weeks ago but it was just too complicated to do. I wanted to implement some tailing of that log file and parse it but when you run it in a thread, reading was blocking operation so I was not able to kill that thread then because it was not interruptible. So that nio stuff was another option which is able to do this but I gave it up in the middle. This approach is way to go, HTH was (Author: smikloso): I tried to implement this as described above some weeks ago but it was just too complicated to do. I wanted to implement some tailing of that log file and parse it but when you run it in a thread, reading was blocking operation it I was not able to kill that thread then because it was not interruptible. So that nio stuff was another option which is able to do this but it gave it up in the middle. This approach is way to go, HTH > Add possibility to report AS console output related to test methods > ------------------------------------------------------------------- > > Key: ARQ-1728 > URL: https://issues.jboss.org/browse/ARQ-1728 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > > There is not any possiblity to see what AS has written out to console with test methods. > Investigate a way how to match output from AS with particular test method during which that console output has occured. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 11 08:44:30 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 11 Aug 2014 08:44:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991978#comment-12991978 ] Stefan Miklosovic edited comment on ARQ-1728 at 8/11/14 8:44 AM: ----------------------------------------------------------------- I tried to implement this as described above some weeks ago but it was just too complicated to do. I wanted to implement some tailing of that log file and parse it but when you run it in a thread, reading was blocking operation so I was not able to kill that thread then because it was not interruptible. So that nio stuff was another option which is able to do this but I gave it up in the middle. This approach is way to go, HTH Maybe [~jhuska] could do this in his spare time as a logging guy ;) was (Author: smikloso): I tried to implement this as described above some weeks ago but it was just too complicated to do. I wanted to implement some tailing of that log file and parse it but when you run it in a thread, reading was blocking operation so I was not able to kill that thread then because it was not interruptible. So that nio stuff was another option which is able to do this but I gave it up in the middle. This approach is way to go, HTH > Add possibility to report AS console output related to test methods > ------------------------------------------------------------------- > > Key: ARQ-1728 > URL: https://issues.jboss.org/browse/ARQ-1728 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > > There is not any possiblity to see what AS has written out to console with test methods. > Investigate a way how to match output from AS with particular test method during which that console output has occured. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 07:44:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 12 Aug 2014 07:44:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1839) Reporter: if test does not have screenshots then next test report has wrong indentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQ-1839: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-recorder/pull/9 > Reporter: if test does not have screenshots then next test report has wrong indentation > --------------------------------------------------------------------------------------- > > Key: ARQ-1839 > URL: https://issues.jboss.org/browse/ARQ-1839 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Trivial > Attachments: wrongIndentation.png > > > Please see screenshot for more information what I mean. > There is probably some small CSS issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 07:44:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 12 Aug 2014 07:44:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1831) Make reported exception stack-traces more concise In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQ-1831: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-recorder/pull/9 > Make reported exception stack-traces more concise > ------------------------------------------------- > > Key: ARQ-1831 > URL: https://issues.jboss.org/browse/ARQ-1831 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Minor > > Reported exceptions stack-traces are too long, they sometimes take more then two screens. It makes report less readable. > It would be nice if they are shorter. > For example if they are generated to {{html}}: > * then they can be written inside {{textarea}} or another block, frame with predefined height, so one will be able to scroll in such a block to reveal full stack-trace > * or something like Twitter Bootstrap [collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 07:44:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 12 Aug 2014 07:44:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1831) Make reported exception stack-traces more concise In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992244#comment-12992244 ] Juraj H?ska commented on ARQ-1831: ---------------------------------- Linked PR. > Make reported exception stack-traces more concise > ------------------------------------------------- > > Key: ARQ-1831 > URL: https://issues.jboss.org/browse/ARQ-1831 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Minor > > Reported exceptions stack-traces are too long, they sometimes take more then two screens. It makes report less readable. > It would be nice if they are shorter. > For example if they are generated to {{html}}: > * then they can be written inside {{textarea}} or another block, frame with predefined height, so one will be able to scroll in such a block to reveal full stack-trace > * or something like Twitter Bootstrap [collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 07:46:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 12 Aug 2014 07:46:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1831) Make reported exception stack-traces more concise In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992244#comment-12992244 ] Juraj H?ska edited comment on ARQ-1831 at 8/12/14 7:45 AM: ----------------------------------------------------------- Linked PR. I made to show only about 10 lines of stacktrace, first line is bold and bigger, and the stacktrace is scrollable after a click (there is a popup which encourages a tester to click on the stacktrace in order to make it scrollable). was (Author: jhuska): Linked PR. > Make reported exception stack-traces more concise > ------------------------------------------------- > > Key: ARQ-1831 > URL: https://issues.jboss.org/browse/ARQ-1831 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Minor > > Reported exceptions stack-traces are too long, they sometimes take more then two screens. It makes report less readable. > It would be nice if they are shorter. > For example if they are generated to {{html}}: > * then they can be written inside {{textarea}} or another block, frame with predefined height, so one will be able to scroll in such a block to reveal full stack-trace > * or something like Twitter Bootstrap [collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 07:46:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 12 Aug 2014 07:46:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1839) Reporter: if test does not have screenshots then next test report has wrong indentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992245#comment-12992245 ] Juraj H?ska commented on ARQ-1839: ---------------------------------- Linked PR which fixes the small CSS issue. > Reporter: if test does not have screenshots then next test report has wrong indentation > --------------------------------------------------------------------------------------- > > Key: ARQ-1839 > URL: https://issues.jboss.org/browse/ARQ-1839 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Trivial > Attachments: wrongIndentation.png > > > Please see screenshot for more information what I mean. > There is probably some small CSS issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 08:54:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 12 Aug 2014 08:54:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1831) Make reported exception stack-traces more concise In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1831: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: recorder_1.0.0.Beta1 Resolution: Done > Make reported exception stack-traces more concise > ------------------------------------------------- > > Key: ARQ-1831 > URL: https://issues.jboss.org/browse/ARQ-1831 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Minor > Fix For: recorder_1.0.0.Beta1 > > > Reported exceptions stack-traces are too long, they sometimes take more then two screens. It makes report less readable. > It would be nice if they are shorter. > For example if they are generated to {{html}}: > * then they can be written inside {{textarea}} or another block, frame with predefined height, so one will be able to scroll in such a block to reveal full stack-trace > * or something like Twitter Bootstrap [collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 08:54:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 12 Aug 2014 08:54:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1839) Reporter: if test does not have screenshots then next test report has wrong indentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1839: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: recorder_1.0.0.Beta1 Resolution: Done > Reporter: if test does not have screenshots then next test report has wrong indentation > --------------------------------------------------------------------------------------- > > Key: ARQ-1839 > URL: https://issues.jboss.org/browse/ARQ-1839 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Trivial > Fix For: recorder_1.0.0.Beta1 > > Attachments: wrongIndentation.png > > > Please see screenshot for more information what I mean. > There is probably some small CSS issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 07:40:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 13 Aug 2014 07:40:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1830) Only the last Test Class of some subset of Test classes is reported with TestNG runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992569#comment-12992569 ] Juraj H?ska commented on ARQ-1830: ---------------------------------- The thing is that when executing subset of some TestNG suite, {{AfterSuite}} is fired for every Test Class - therefore report is exported twice, and only report for the last Test Class is kept. For JUnit, the {{AfterSuite}} is fired only once - expected behavior. Just a note that this behavior of TestNG suite is occurring only when executing some subset of tests, e.g. {{-Dtest=OnTestClass,OtherTestClass}}. Is this an Arquillian bug I should report ? Any insight [~smikloso] [~kpiwko] please ? > Only the last Test Class of some subset of Test classes is reported with TestNG runner > -------------------------------------------------------------------------------------- > > Key: ARQ-1830 > URL: https://issues.jboss.org/browse/ARQ-1830 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > > When you have TestNG test suite, after running some *subset* of all test classes (particular test classes or e.g. all classes in one package), then only the last test class is reported. > It works when you run all tests, and also with JUnit nicely. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 08:14:31 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 13 Aug 2014 08:14:31 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1830) Only the last Test Class of some subset of Test classes is reported with TestNG runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992584#comment-12992584 ] Karel Piwko commented on ARQ-1830: ---------------------------------- It is likely a bug or behavior caused by TestNG runner in Surefire. Anyway that's something what should be fixed in core, especially if it works fine with TestNG. [~jhuska] is this behavior consistent across ARQ Core versions? > Only the last Test Class of some subset of Test classes is reported with TestNG runner > -------------------------------------------------------------------------------------- > > Key: ARQ-1830 > URL: https://issues.jboss.org/browse/ARQ-1830 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha4 > Reporter: Juraj H?ska > > When you have TestNG test suite, after running some *subset* of all test classes (particular test classes or e.g. all classes in one package), then only the last test class is reported. > It works when you run all tests, and also with JUnit nicely. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 15:44:29 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 13 Aug 2014 15:44:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1800) SQL scripts are loaded with the default charset In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-1800 started by Bartosz Majsak. > SQL scripts are loaded with the default charset > ----------------------------------------------- > > Key: ARQ-1800 > URL: https://issues.jboss.org/browse/ARQ-1800 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: jean-fran?ois Lefebvre > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > SQLSripts are loaded with the default plateform charset. > Could you please add a property like this : > > XXX > > to set the default scripts encoding. > see org.jboss.arquillian.persistence.script.ScriptLoader > reader = new BufferedReader(new InputStreamReader(inputStream)); -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 15 04:56:30 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 15 Aug 2014 04:56:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1800) SQL scripts are loaded with the default charset In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak resolved ARQ-1800. --------------------------------- Resolution: Done Pushed [upstream|https://github.com/arquillian/arquillian-extension-persistence/commit/915e068cdea074590dfdb2d6d653702303f195c1]. > SQL scripts are loaded with the default charset > ----------------------------------------------- > > Key: ARQ-1800 > URL: https://issues.jboss.org/browse/ARQ-1800 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: jean-fran?ois Lefebvre > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > SQLSripts are loaded with the default plateform charset. > Could you please add a property like this : > > XXX > > to set the default scripts encoding. > see org.jboss.arquillian.persistence.script.ScriptLoader > reader = new BufferedReader(new InputStreamReader(inputStream)); -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 15 05:30:29 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 15 Aug 2014 05:30:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1815) Unable to locate Oracle Sequence filter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1815: -------------------------------- Fix Version/s: persistence_1.0.0.next (was: persistence_1.0.0.Alpha7) > Unable to locate Oracle Sequence filter > --------------------------------------- > > Key: ARQ-1815 > URL: https://issues.jboss.org/browse/ARQ-1815 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Blocker > Fix For: persistence_1.0.0.next > > > When trying to define custom table filter using > {{org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider}} > It's resulting in > {{Unable to find sequence filter for org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider. Using default database sequence filter.}} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 15 13:48:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 15 Aug 2014 13:48:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-458) Graphene can't be compiled in Maven 3.1.1 In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-458: --------------------------------- Summary: Graphene can't be compiled in Maven 3.1.1 Key: ARQGRA-458 URL: https://issues.jboss.org/browse/ARQGRA-458 Project: Arquillian Graphene Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Luk?? Fry? -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 08:39:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 19 Aug 2014 08:39:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1841) Spacelift can not deal with background process invocation In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1841: -------------------------------------- Summary: Spacelift can not deal with background process invocation Key: ARQ-1841 URL: https://issues.jboss.org/browse/ARQ-1841 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Spacelift Affects Versions: spacelift_1.0.0.Alpha2 Reporter: Stefan Miklosovic Let's have this simple script: {code} #!/bin/sh curpath=`dirname $0` nohup ${curpath}/run_agent.sh $@ > /dev/null & 2>&1 {code} I execute it like this: {code} public class App { public static void main(String[] args) throws IOException { Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory()); System.out.println("before"); Tasks.prepare(CommandTool.class) .programName("/bin/bash") .parameters("-c", "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh") .execute().await(); System.out.println("after"); } } {code} So it effectively does this: {code} /bin/bash -c "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh" {code} However it never reaches "after" output, that process in the script is started but Spacelift does not send it to the background and it still waits untill it is finished which never happen. Executing that script directly like following does the job: {code} public class App { public static void main(String[] args) throws IOException { Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory()); System.out.println("before"); Runtime.getRuntime().exec("/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh"); System.out.println("after"); } } {code} Started process survives JVM termination. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 08:43:32 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 19 Aug 2014 08:43:32 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1841) Spacelift can not deal with background process invocation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1841: ----------------------------------- Description: Let's have this simple script: {code:title=run_agent_bg.sh|borderStyle=solid} #!/bin/sh curpath=`dirname $0` nohup ${curpath}/run_agent.sh $@ > /dev/null & 2>&1 {code} I execute it like this: {code:title=App.java|borderStyle=solid} public class App { public static void main(String[] args) throws IOException { Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory()); System.out.println("before"); Tasks.prepare(CommandTool.class) .programName("/bin/bash") .parameters("-c", "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh") .execute().await(); System.out.println("after"); } } {code} So it effectively does this: {code} /bin/bash -c "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh" {code} However it never reaches "after" output, that process in the script is started but Spacelift does not send it to the background and it still waits untill it is finished which never happen. Executing that script directly like following does the job: {code:title=App.java|borderStyle=solid} public class App { public static void main(String[] args) throws IOException { Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory()); System.out.println("before"); Runtime.getRuntime().exec("/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh"); System.out.println("after"); } } {code} Started process survives JVM termination. was: Let's have this simple script: {code} #!/bin/sh curpath=`dirname $0` nohup ${curpath}/run_agent.sh $@ > /dev/null & 2>&1 {code} I execute it like this: {code} public class App { public static void main(String[] args) throws IOException { Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory()); System.out.println("before"); Tasks.prepare(CommandTool.class) .programName("/bin/bash") .parameters("-c", "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh") .execute().await(); System.out.println("after"); } } {code} So it effectively does this: {code} /bin/bash -c "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh" {code} However it never reaches "after" output, that process in the script is started but Spacelift does not send it to the background and it still waits untill it is finished which never happen. Executing that script directly like following does the job: {code} public class App { public static void main(String[] args) throws IOException { Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory()); System.out.println("before"); Runtime.getRuntime().exec("/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh"); System.out.println("after"); } } {code} Started process survives JVM termination. > Spacelift can not deal with background process invocation > --------------------------------------------------------- > > Key: ARQ-1841 > URL: https://issues.jboss.org/browse/ARQ-1841 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > > Let's have this simple script: > {code:title=run_agent_bg.sh|borderStyle=solid} > #!/bin/sh > curpath=`dirname $0` > nohup ${curpath}/run_agent.sh $@ > /dev/null & 2>&1 > {code} > I execute it like this: > {code:title=App.java|borderStyle=solid} > public class App { > public static void main(String[] args) throws IOException { > Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory()); > System.out.println("before"); > Tasks.prepare(CommandTool.class) > .programName("/bin/bash") > .parameters("-c", "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh") > .execute().await(); > > System.out.println("after"); > } > } > {code} > So it effectively does this: > {code} > /bin/bash -c "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh" > {code} > However it never reaches "after" output, that process in the script is started but Spacelift does not send it to the background and it still waits untill it is finished which never happen. > Executing that script directly like following does the job: > {code:title=App.java|borderStyle=solid} > public class App { > public static void main(String[] args) throws IOException { > Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory()); > System.out.println("before"); > Runtime.getRuntime().exec("/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh"); > > System.out.println("after"); > } > } > {code} > Started process survives JVM termination. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 08:49:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 19 Aug 2014 08:49:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1841) Spacelift can not deal with background process invocation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993901#comment-12993901 ] Stefan Miklosovic commented on ARQ-1841: ---------------------------------------- https://github.com/smiklosovic/spacelift-hanging > Spacelift can not deal with background process invocation > --------------------------------------------------------- > > Key: ARQ-1841 > URL: https://issues.jboss.org/browse/ARQ-1841 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > > Let's have this simple script: > {code:title=run_agent_bg.sh|borderStyle=solid} > #!/bin/sh > curpath=`dirname $0` > nohup ${curpath}/run_agent.sh $@ > /dev/null & 2>&1 > {code} > I execute it like this: > {code:title=App.java|borderStyle=solid} > public class App { > public static void main(String[] args) throws IOException { > Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory()); > System.out.println("before"); > Tasks.prepare(CommandTool.class) > .programName("/bin/bash") > .parameters("-c", "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh") > .execute().await(); > > System.out.println("after"); > } > } > {code} > So it effectively does this: > {code} > /bin/bash -c "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh" > {code} > However it never reaches "after" output, that process in the script is started but Spacelift does not send it to the background and it still waits untill it is finished which never happen. > Executing that script directly like following does the job: > {code:title=App.java|borderStyle=solid} > public class App { > public static void main(String[] args) throws IOException { > Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory()); > System.out.println("before"); > Runtime.getRuntime().exec("/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh"); > > System.out.println("after"); > } > } > {code} > Started process survives JVM termination. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 23:53:29 2014 From: issues at jboss.org (Alexandr Sokolov (JIRA)) Date: Wed, 20 Aug 2014 23:53:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1842) Show original exception instead of NullPointerExcetpion from TransactionHandler In-Reply-To: References: Message-ID: Alexandr Sokolov created ARQ-1842: ------------------------------------- Summary: Show original exception instead of NullPointerExcetpion from TransactionHandler Key: ARQ-1842 URL: https://issues.jboss.org/browse/ARQ-1842 Project: Arquillian Issue Type: Sub-task Reporter: Alexandr Sokolov Arquillan architecture based on observers. But now, if one of observers throws an exception and transactions are used. We are getting: java.lang.NullPointerException: null at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.testRequiresRollbackDueToFailure(TransactionHandler.java:170) Although the actual exception in my case was thrown by DBUnitDataHandler.prepare(). Could you please change the logic so the original exception is displayed in the output? Otherwise we have to debug to get the actual exception. There is no way to find a solution without debugging via arquillian classes. It really takes rather long time. Full exception log: {code} java.lang.NullPointerException: null at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.testRequiresRollbackDueToFailure(TransactionHandler.java:170) at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.rollbackRequired(TransactionHandler.java:159) at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.endTransaction(TransactionHandler.java:123) at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.endTransactionAfterTest(TransactionHandler.java:102) 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:606) 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:606) 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:102) 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:606) 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:84) 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:606) 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:65) 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:606) 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:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:277) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) at org.junit.runner.JUnitCore.run(JUnitCore.java:160) at org.junit.runner.JUnitCore.run(JUnitCore.java:138) at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66) at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:159) at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:125) at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:89) at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) at java.lang.Thread.run(Thread.java:744) {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 21 09:46:00 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 21 Aug 2014 09:46:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1842) Show original exception instead of NullPointerExcetpion from TransactionHandler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994737#comment-12994737 ] Aslak Knutsen commented on ARQ-1842: ------------------------------------ I think this is related to https://issues.jboss.org/browse/ARQ-1807 Could you verify with arquillian-core upstream master branch? > Show original exception instead of NullPointerExcetpion from TransactionHandler > ------------------------------------------------------------------------------- > > Key: ARQ-1842 > URL: https://issues.jboss.org/browse/ARQ-1842 > Project: Arquillian > Issue Type: Sub-task > Components: Base Implementation > Reporter: Alexandr Sokolov > Fix For: 2.0.0.CR1 > > > Arquillan architecture based on observers. But now, if one of observers throws an exception and transactions are used. We are getting: > > java.lang.NullPointerException: null > at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.testRequiresRollbackDueToFailure(TransactionHandler.java:170) > > Although the actual exception in my case was thrown by DBUnitDataHandler.prepare(). > > Could you please change the logic so the original exception is displayed in the output? Otherwise we have to debug to get the actual exception. There is no way to find a solution without debugging via arquillian classes. It really takes rather long time. > Full exception log: > {code} > java.lang.NullPointerException: null > at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.testRequiresRollbackDueToFailure(TransactionHandler.java:170) > at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.rollbackRequired(TransactionHandler.java:159) > at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.endTransaction(TransactionHandler.java:123) > at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.endTransactionAfterTest(TransactionHandler.java:102) > 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:606) > 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:606) > 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:102) > 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:606) > 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:84) > 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:606) > 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:65) > 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:606) > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:277) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:159) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:125) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:89) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) > at java.lang.Thread.run(Thread.java:744) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 21 09:52:00 2014 From: issues at jboss.org (SBS JIRA Integration (JIRA)) Date: Thu, 21 Aug 2014 09:52:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1842) Show original exception instead of NullPointerExcetpion from TransactionHandler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SBS JIRA Integration updated ARQ-1842: -------------------------------------- Forum Reference: https://community.jboss.org/message/901475#901475 > Show original exception instead of NullPointerExcetpion from TransactionHandler > ------------------------------------------------------------------------------- > > Key: ARQ-1842 > URL: https://issues.jboss.org/browse/ARQ-1842 > Project: Arquillian > Issue Type: Sub-task > Components: Base Implementation > Reporter: Alexandr Sokolov > Fix For: 2.0.0.CR1 > > > Arquillan architecture based on observers. But now, if one of observers throws an exception and transactions are used. We are getting: > > java.lang.NullPointerException: null > at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.testRequiresRollbackDueToFailure(TransactionHandler.java:170) > > Although the actual exception in my case was thrown by DBUnitDataHandler.prepare(). > > Could you please change the logic so the original exception is displayed in the output? Otherwise we have to debug to get the actual exception. There is no way to find a solution without debugging via arquillian classes. It really takes rather long time. > Full exception log: > {code} > java.lang.NullPointerException: null > at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.testRequiresRollbackDueToFailure(TransactionHandler.java:170) > at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.rollbackRequired(TransactionHandler.java:159) > at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.endTransaction(TransactionHandler.java:123) > at org.jboss.arquillian.transaction.impl.lifecycle.TransactionHandler.endTransactionAfterTest(TransactionHandler.java:102) > 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:606) > 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:606) > 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:102) > 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:606) > 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:84) > 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:606) > 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:65) > 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:606) > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:277) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:159) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:125) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:89) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) > at java.lang.Thread.run(Thread.java:744) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Wed Aug 27 10:08:00 2014 From: issues at jboss.org (Tilmann Kuhn (JIRA)) Date: Wed, 27 Aug 2014 10:08:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996148#comment-12996148 ] Tilmann Kuhn commented on ARQGRA-454: ------------------------------------- I have the same issue. I think the key information here is that this happens in an @Before method of the test. Though I didn't have time to create a minimum example to reproduce yet. I just checked with the debugger: Not visible in the stacktrace above is that the problem actually occurs in ManagerImpl.resolve(GrapheneConfiguration.class) when querying get() of Instance The GrapheneConfiguration is stored in ClassContext and at this point the only active context is ApplicationContext. Hence GrapheneConfiguration is not found and null returned by the ManagerImpl. Maybe this is connected to the changes in core connected to the support of Junit Rules? WebDriver.navigate().to(...) works in @Before and can be used as a workaround if you have fixed server configuration. > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Wed Aug 27 10:08:59 2014 From: issues at jboss.org (Tilmann Kuhn (JIRA)) Date: Wed, 27 Aug 2014 10:08:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996148#comment-12996148 ] Tilmann Kuhn edited comment on ARQGRA-454 at 8/27/14 10:08 AM: --------------------------------------------------------------- I have the same issue. I think the key information here is that this happens in an @Before method of the test. Though I didn't have time to create a minimum example to reproduce yet. I just checked with the debugger: Not visible in the stacktrace above is that the problem actually occurs in ManagerImpl.resolve(GrapheneConfiguration.class) while resolving the get() of Instance The GrapheneConfiguration is stored in ClassContext and at this point the only active context is ApplicationContext. Hence GrapheneConfiguration is not found and null returned by the ManagerImpl. Maybe this is connected to the changes in core connected to the support of Junit Rules? WebDriver.navigate().to(...) works in @Before and can be used as a workaround if you have fixed server configuration. was (Author: tilm4nn): I have the same issue. I think the key information here is that this happens in an @Before method of the test. Though I didn't have time to create a minimum example to reproduce yet. I just checked with the debugger: Not visible in the stacktrace above is that the problem actually occurs in ManagerImpl.resolve(GrapheneConfiguration.class) when querying get() of Instance The GrapheneConfiguration is stored in ClassContext and at this point the only active context is ApplicationContext. Hence GrapheneConfiguration is not found and null returned by the ManagerImpl. Maybe this is connected to the changes in core connected to the support of Junit Rules? WebDriver.navigate().to(...) works in @Before and can be used as a workaround if you have fixed server configuration. > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Wed Aug 27 10:35:00 2014 From: issues at jboss.org (Tilmann Kuhn (JIRA)) Date: Wed, 27 Aug 2014 10:35:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996171#comment-12996171 ] Tilmann Kuhn commented on ARQGRA-454: ------------------------------------- Ok, this happens with graphene 2.0.3 as with 2.1.0.Alpha1. Minimum example to reproduce: @RunWith(Arquillian.class) public class NpeTest { @Location("foobar") public static class Page { } @Before public void throws_npe_due_to_missing_GrapheneConfiguration() { Graphene.goTo(Page.class); } @RunAsClient @Test public void just_needed_to_execute_at_before() { } } > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Wed Aug 27 10:37:00 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 27 Aug 2014 10:37:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996171#comment-12996171 ] Luk?? Fry? edited comment on ARQGRA-454 at 8/27/14 10:36 AM: ------------------------------------------------------------- Ok, this happens with graphene 2.0.3 as with 2.1.0.Alpha1. Minimum example to reproduce: {code} @RunWith(Arquillian.class) public class NpeTest { @Location("foobar") public static class Page { } @Before public void throws_npe_due_to_missing_GrapheneConfiguration() { Graphene.goTo(Page.class); } @RunAsClient @Test public void just_needed_to_execute_at_before() { } } {code} was (Author: tilm4nn): Ok, this happens with graphene 2.0.3 as with 2.1.0.Alpha1. Minimum example to reproduce: @RunWith(Arquillian.class) public class NpeTest { @Location("foobar") public static class Page { } @Before public void throws_npe_due_to_missing_GrapheneConfiguration() { Graphene.goTo(Page.class); } @RunAsClient @Test public void just_needed_to_execute_at_before() { } } > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Wed Aug 27 10:38:00 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 27 Aug 2014 10:38:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-454: ------------------------------ Fix Version/s: 2.0.4.Final > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > Fix For: 2.0.4.Final > > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Wed Aug 27 10:38:01 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 27 Aug 2014 10:38:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996175#comment-12996175 ] Luk?? Fry? commented on ARQGRA-454: ----------------------------------- Thanks for reproducer, Tilmann! > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > Fix For: 2.0.4.Final > > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 05:35:00 2014 From: issues at jboss.org (Tilmann Kuhn (JIRA)) Date: Thu, 28 Aug 2014 05:35:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996386#comment-12996386 ] Tilmann Kuhn commented on ARQGRA-454: ------------------------------------- You are welcome :) For completeness another one with a rule. In addition I think there is also @After and of cour @BeforeClass, @AfterClass etc... {code} @RunWith(Arquillian.class) public class NpeTestWithRule { @Location("foobar") public static class Page { } @Rule public ExternalResource goToRule = new ExternalResource() { @Override protected void before() throws Throwable { Graphene.goTo(Page.class); } }; @RunAsClient @Test public void just_needed_to_execute_rule() { } } {/code} > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > Fix For: 2.0.4.Final > > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 05:35:01 2014 From: issues at jboss.org (Tilmann Kuhn (JIRA)) Date: Thu, 28 Aug 2014 05:35:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996386#comment-12996386 ] Tilmann Kuhn edited comment on ARQGRA-454 at 8/28/14 5:34 AM: -------------------------------------------------------------- You are welcome :) For completeness another one with a rule. In addition I think there is also @After and of cour @BeforeClass, @AfterClass etc... {code} @RunWith(Arquillian.class) public class NpeTestWithRule { @Location("foobar") public static class Page { } @Rule public ExternalResource goToRule = new ExternalResource() { @Override protected void before() throws Throwable { Graphene.goTo(Page.class); } }; @RunAsClient @Test public void just_needed_to_execute_rule() { } } {code} was (Author: tilm4nn): You are welcome :) For completeness another one with a rule. In addition I think there is also @After and of cour @BeforeClass, @AfterClass etc... {code} @RunWith(Arquillian.class) public class NpeTestWithRule { @Location("foobar") public static class Page { } @Rule public ExternalResource goToRule = new ExternalResource() { @Override protected void before() throws Throwable { Graphene.goTo(Page.class); } }; @RunAsClient @Test public void just_needed_to_execute_rule() { } } {/code} > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > Fix For: 2.0.4.Final > > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 06:33:00 2014 From: issues at jboss.org (Tilmann Kuhn (JIRA)) Date: Thu, 28 Aug 2014 06:33:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996386#comment-12996386 ] Tilmann Kuhn edited comment on ARQGRA-454 at 8/28/14 6:32 AM: -------------------------------------------------------------- You are welcome :) For completeness another one with a rule. In addition I think there is also @After and of course @BeforeClass, @AfterClass etc... are before and after class supported at all? {code} @RunWith(Arquillian.class) public class NpeTestWithRule { @Location("foobar") public static class Page { } @Rule public ExternalResource goToRule = new ExternalResource() { @Override protected void before() throws Throwable { Graphene.goTo(Page.class); } }; @RunAsClient @Test public void just_needed_to_execute_rule() { } } {code} was (Author: tilm4nn): You are welcome :) For completeness another one with a rule. In addition I think there is also @After and of cour @BeforeClass, @AfterClass etc... {code} @RunWith(Arquillian.class) public class NpeTestWithRule { @Location("foobar") public static class Page { } @Rule public ExternalResource goToRule = new ExternalResource() { @Override protected void before() throws Throwable { Graphene.goTo(Page.class); } }; @RunAsClient @Test public void just_needed_to_execute_rule() { } } {code} > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > Fix For: 2.0.4.Final > > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 18:49:59 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 28 Aug 2014 18:49:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-506) Support more complex property types in container configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-506: ------------------------------ Fix Version/s: 2.0.0.Beta1 > Support more complex property types in container configuration > -------------------------------------------------------------- > > Key: ARQ-506 > URL: https://issues.jboss.org/browse/ARQ-506 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Configuration > Affects Versions: 1.0.0.Final > Reporter: Gerhard Poul > Fix For: 2.0.0.Beta1 > > > It might sometimes be helpful to support arbitrary property lists within an arquillian configuration, such as when we want to make it possible to pass properties to the underlying container implementations, but that have no effect on the behavior of the arquillian-container-implementation itself. > This is not to replace, but to augment the current configuration capability, such that we can provide something like the following in an arquillian.xml: > > > > > > ... > > someValue > > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 20:06:59 2014 From: issues at jboss.org (Ian Brandt (JIRA)) Date: Thu, 28 Aug 2014 20:06:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1843) Tomcat managed container ignores javaHome configuration In-Reply-To: References: Message-ID: Ian Brandt created ARQ-1843: ------------------------------- Summary: Tomcat managed container ignores javaHome configuration Key: ARQ-1843 URL: https://issues.jboss.org/browse/ARQ-1843 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR7 Reporter: Ian Brandt The {{javaHome}} property in {{CommonTomcatManagedConfiguration}} is being ignored by {{CommonTomcatManagedContainer}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 20:06:59 2014 From: issues at jboss.org (Ian Brandt (JIRA)) Date: Thu, 28 Aug 2014 20:06:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1843) Tomcat managed container ignores javaHome configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Brandt reassigned ARQ-1843: ------------------------------- Assignee: Ian Brandt > Tomcat managed container ignores javaHome configuration > ------------------------------------------------------- > > Key: ARQ-1843 > URL: https://issues.jboss.org/browse/ARQ-1843 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > > The {{javaHome}} property in {{CommonTomcatManagedConfiguration}} is being ignored by {{CommonTomcatManagedContainer}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 20:07:59 2014 From: issues at jboss.org (Ian Brandt (JIRA)) Date: Thu, 28 Aug 2014 20:07:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1843) Tomcat managed container ignores javaHome configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Brandt updated ARQ-1843: ---------------------------- Fix Version/s: 1.0.0.Final > Tomcat managed container ignores javaHome configuration > ------------------------------------------------------- > > Key: ARQ-1843 > URL: https://issues.jboss.org/browse/ARQ-1843 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: 1.0.0.Final > > > The {{javaHome}} property in {{CommonTomcatManagedConfiguration}} is being ignored by {{CommonTomcatManagedContainer}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 20:09:59 2014 From: issues at jboss.org (Ian Brandt (JIRA)) Date: Thu, 28 Aug 2014 20:09:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1843) Tomcat managed container ignores javaHome configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Brandt resolved ARQ-1843. ----------------------------- Resolution: Done Fixed by https://github.com/arquillian/arquillian-container-tomcat/commit/620a4f7a37194667518700d070046efa9d3ad06c. > Tomcat managed container ignores javaHome configuration > ------------------------------------------------------- > > Key: ARQ-1843 > URL: https://issues.jboss.org/browse/ARQ-1843 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: 1.0.0.Final > > > The {{javaHome}} property in {{CommonTomcatManagedConfiguration}} is being ignored by {{CommonTomcatManagedContainer}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 29 04:59:00 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 29 Aug 2014 04:59:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1444) Oracle does not support query delimiter inside statements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996850#comment-12996850 ] Bartosz Majsak commented on ARQ-1444: ------------------------------------- I will look at BEFORE hiding the exception. Thanks for spotting that. > Oracle does not support query delimiter inside statements > --------------------------------------------------------- > > Key: ARQ-1444 > URL: https://issues.jboss.org/browse/ARQ-1444 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Environment: Oracle Database. > Reporter: Michel Graciano > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > When we try to use @ApplyScriptBefore and the script file has more than one statement, we use ; as delimiter. The problem is that the delimiter is not removed from the statement before run it, so Oracle database return the following exception: > Caused by: java.sql.SQLSyntaxErrorException: ORA-00911: invalid character -- This message was sent by Atlassian JIRA (v6.3.1#6329)