From issues at jboss.org Fri Jan 8 13:50:00 2016 From: issues at jboss.org (Anthony Smith (JIRA)) Date: Fri, 8 Jan 2016 13:50:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-127) Verify TestNG Parallel test exeuction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146621#comment-13146621 ] Anthony Smith commented on ARQ-127: ----------------------------------- [~tremes] adding arquillian to the test groups is required, but does NOT resolve the TestRunner & Nullpointer exceptions. link to my post [#https://developer.jboss.org/thread/266910] > Verify TestNG Parallel test exeuction > ------------------------------------- > > Key: ARQ-127 > URL: https://issues.jboss.org/browse/ARQ-127 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Performance, Test Harness Integration > Reporter: Aslak Knutsen > Assignee: St?le Pedersen > Priority: Critical > Fix For: 2.0.0.Beta1 > > Attachments: testng-parallel.zip > > > Verify that Arquillian behaves correctly when ran in TestNG Parallel modes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 8 13:51:00 2016 From: issues at jboss.org (Anthony Smith (JIRA)) Date: Fri, 8 Jan 2016 13:51:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-127) Verify TestNG Parallel test exeuction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146621#comment-13146621 ] Anthony Smith edited comment on ARQ-127 at 1/8/16 1:50 PM: ----------------------------------------------------------- [~tremes] adding arquillian to the test groups is required, but does NOT resolve the TestRunner & Nullpointer exceptions. link to my post [#anchor]https://developer.jboss.org/thread/266910 [#https://developer.jboss.org/thread/266910] was (Author: testgroupie): [~tremes] adding arquillian to the test groups is required, but does NOT resolve the TestRunner & Nullpointer exceptions. link to my post [#https://developer.jboss.org/thread/266910] > Verify TestNG Parallel test exeuction > ------------------------------------- > > Key: ARQ-127 > URL: https://issues.jboss.org/browse/ARQ-127 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Performance, Test Harness Integration > Reporter: Aslak Knutsen > Assignee: St?le Pedersen > Priority: Critical > Fix For: 2.0.0.Beta1 > > Attachments: testng-parallel.zip > > > Verify that Arquillian behaves correctly when ran in TestNG Parallel modes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 8 13:52:00 2016 From: issues at jboss.org (Anthony Smith (JIRA)) Date: Fri, 8 Jan 2016 13:52:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-127) Verify TestNG Parallel test exeuction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146621#comment-13146621 ] Anthony Smith edited comment on ARQ-127 at 1/8/16 1:51 PM: ----------------------------------------------------------- [~tremes] adding arquillian to the test groups is required, but does NOT resolve the TestRunner & Nullpointer exceptions. link to my post [https://developer.jboss.org/thread/266910] was (Author: testgroupie): [~tremes] adding arquillian to the test groups is required, but does NOT resolve the TestRunner & Nullpointer exceptions. link to my post [#anchor]https://developer.jboss.org/thread/266910 [#https://developer.jboss.org/thread/266910] > Verify TestNG Parallel test exeuction > ------------------------------------- > > Key: ARQ-127 > URL: https://issues.jboss.org/browse/ARQ-127 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Performance, Test Harness Integration > Reporter: Aslak Knutsen > Assignee: St?le Pedersen > Priority: Critical > Fix For: 2.0.0.Beta1 > > Attachments: testng-parallel.zip > > > Verify that Arquillian behaves correctly when ran in TestNG Parallel modes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 12 03:02:00 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 12 Jan 2016 03:02:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-486) When HTTP or AJAX request is in progress and guard fails, report that the timeout increase is necessary In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-486: --------------------------------- Summary: When HTTP or AJAX request is in progress and guard fails, report that the timeout increase is necessary Key: ARQGRA-486 URL: https://issues.jboss.org/browse/ARQGRA-486 Project: Arquillian Graphene Issue Type: Enhancement Reporter: Luk?? Fry? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 12 09:33:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 12 Jan 2016 09:33:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2006) ISE when manual deployment is used In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2006: ----------------------------------- Summary: ISE when manual deployment is used Key: ARQ-2006 URL: https://issues.jboss.org/browse/ARQ-2006 Project: Arquillian Issue Type: Bug Components: Extension - Drone Affects Versions: drone_2.0.0.Alpha5 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.0.0.Beta1 Consider these scenarios: 1) {code:java} @Deployment(name = "first", managed = false) public static Archive deployFirst() { return ShrinkWrap.create(WebArchive.class); } @Deployment(name = "second") public static WebArchive deploySecond() { return ShrinkWrap.create(WebArchive.class); } @ArquillianResource private Deployer deployer; @Drone @OperateOnDeployment("first") private WebDriver firstBrowser; @Drone @OperateOnDeployment("second") private WebDriver secondBrowser; @Test @InSequence(1) public void runFirstTest() throws InterruptedException { deployer.deploy("first"); firstBrowser.get("http://google.com"); deployer.undeploy("first"); } @Test @InSequence(2) public void runSecondTest() throws InterruptedException { secondBrowser.get("http://google.com"); } {code} 2) {code:java} @Deployment(name = "deployment", managed = false) public static Archive deployFirst() { return ShrinkWrap.create(WebArchive.class); } @ArquillianResource private Deployer deployer; @Drone @OperateOnDeployment("deployment") private WebDriver browser; @Test @InSequence(1) public void runFirstTest() throws InterruptedException { deployer.deploy("deployment"); browser.get("http://google.com"); deployer.undeploy("deployment"); } @Test @InSequence(2) public void runSecondTest() throws InterruptedException { deployer.deploy("deployment"); browser.get("http://google.com"); deployer.undeploy("deployment"); } {code} both of them lead to the IllegalStateException: {noformat} java.lang.IllegalStateException: Injection point DronePointImpl{droneClass=interface org.openqa.selenium.WebDriver, annotations=[@org.jboss.arquillian.drone.api.annotation.Drone(), @org.jboss.arquillian.container.test.api.OperateOnDeployment(value=deployment)], lifecycle=DEPLOYMENT} has deployment lifecycle and has to be prepared in @BeforeClass. at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.ensureInjectionPointPrepared(DroneTestEnrichHelper.java:104) at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.enrichTestClass(DroneTestEnrichHelper.java:72) at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:54) ... {noformat} The cause: the deployment-scoped drone point is destroyed before undeploy, but created only in BeforeClass. In the first test method the drone point is destroyed, however before the second test method is launched the test class is enriched including the drone point that is already destroyed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 12 09:34:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 12 Jan 2016 09:34:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2006) ISE when deployment-scoped drone point and manual deployment is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2006: -------------------------------- Summary: ISE when deployment-scoped drone point and manual deployment is used (was: ISE when manual deployment is used) > ISE when deployment-scoped drone point and manual deployment is used > -------------------------------------------------------------------- > > Key: ARQ-2006 > URL: https://issues.jboss.org/browse/ARQ-2006 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha5 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Beta1 > > > Consider these scenarios: > 1) > {code:java} > @Deployment(name = "first", managed = false) > public static Archive deployFirst() { > return ShrinkWrap.create(WebArchive.class); > } > @Deployment(name = "second") > public static WebArchive deploySecond() { > return ShrinkWrap.create(WebArchive.class); > } > @ArquillianResource > private Deployer deployer; > @Drone > @OperateOnDeployment("first") > private WebDriver firstBrowser; > @Drone > @OperateOnDeployment("second") > private WebDriver secondBrowser; > @Test > @InSequence(1) > public void runFirstTest() throws InterruptedException { > deployer.deploy("first"); > firstBrowser.get("http://google.com"); > deployer.undeploy("first"); > } > @Test > @InSequence(2) > public void runSecondTest() throws InterruptedException { > secondBrowser.get("http://google.com"); > } > {code} > 2) > {code:java} > @Deployment(name = "deployment", managed = false) > public static Archive deployFirst() { > return ShrinkWrap.create(WebArchive.class); > } > @ArquillianResource > private Deployer deployer; > @Drone > @OperateOnDeployment("deployment") > private WebDriver browser; > @Test > @InSequence(1) > public void runFirstTest() throws InterruptedException { > deployer.deploy("deployment"); > browser.get("http://google.com"); > deployer.undeploy("deployment"); > } > @Test > @InSequence(2) > public void runSecondTest() throws InterruptedException { > deployer.deploy("deployment"); > browser.get("http://google.com"); > deployer.undeploy("deployment"); > } > {code} > both of them lead to the IllegalStateException: > {noformat} > java.lang.IllegalStateException: Injection point DronePointImpl{droneClass=interface org.openqa.selenium.WebDriver, annotations=[@org.jboss.arquillian.drone.api.annotation.Drone(), @org.jboss.arquillian.container.test.api.OperateOnDeployment(value=deployment)], lifecycle=DEPLOYMENT} has deployment lifecycle and has to be prepared in @BeforeClass. > at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.ensureInjectionPointPrepared(DroneTestEnrichHelper.java:104) > at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.enrichTestClass(DroneTestEnrichHelper.java:72) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:54) > ... > {noformat} > The cause: the deployment-scoped drone point is destroyed before undeploy, but created only in BeforeClass. In the first test method the drone point is destroyed, however before the second test method is launched the test class is enriched including the drone point that is already destroyed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 12 09:34:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 12 Jan 2016 09:34:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2006) ISE for deployment-scoped drone point when manual deployment is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2006: -------------------------------- Summary: ISE for deployment-scoped drone point when manual deployment is used (was: ISE when deployment-scoped drone point and manual deployment is used) > ISE for deployment-scoped drone point when manual deployment is used > -------------------------------------------------------------------- > > Key: ARQ-2006 > URL: https://issues.jboss.org/browse/ARQ-2006 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha5 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Beta1 > > > Consider these scenarios: > 1) > {code:java} > @Deployment(name = "first", managed = false) > public static Archive deployFirst() { > return ShrinkWrap.create(WebArchive.class); > } > @Deployment(name = "second") > public static WebArchive deploySecond() { > return ShrinkWrap.create(WebArchive.class); > } > @ArquillianResource > private Deployer deployer; > @Drone > @OperateOnDeployment("first") > private WebDriver firstBrowser; > @Drone > @OperateOnDeployment("second") > private WebDriver secondBrowser; > @Test > @InSequence(1) > public void runFirstTest() throws InterruptedException { > deployer.deploy("first"); > firstBrowser.get("http://google.com"); > deployer.undeploy("first"); > } > @Test > @InSequence(2) > public void runSecondTest() throws InterruptedException { > secondBrowser.get("http://google.com"); > } > {code} > 2) > {code:java} > @Deployment(name = "deployment", managed = false) > public static Archive deployFirst() { > return ShrinkWrap.create(WebArchive.class); > } > @ArquillianResource > private Deployer deployer; > @Drone > @OperateOnDeployment("deployment") > private WebDriver browser; > @Test > @InSequence(1) > public void runFirstTest() throws InterruptedException { > deployer.deploy("deployment"); > browser.get("http://google.com"); > deployer.undeploy("deployment"); > } > @Test > @InSequence(2) > public void runSecondTest() throws InterruptedException { > deployer.deploy("deployment"); > browser.get("http://google.com"); > deployer.undeploy("deployment"); > } > {code} > both of them lead to the IllegalStateException: > {noformat} > java.lang.IllegalStateException: Injection point DronePointImpl{droneClass=interface org.openqa.selenium.WebDriver, annotations=[@org.jboss.arquillian.drone.api.annotation.Drone(), @org.jboss.arquillian.container.test.api.OperateOnDeployment(value=deployment)], lifecycle=DEPLOYMENT} has deployment lifecycle and has to be prepared in @BeforeClass. > at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.ensureInjectionPointPrepared(DroneTestEnrichHelper.java:104) > at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.enrichTestClass(DroneTestEnrichHelper.java:72) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:54) > ... > {noformat} > The cause: the deployment-scoped drone point is destroyed before undeploy, but created only in BeforeClass. In the first test method the drone point is destroyed, however before the second test method is launched the test class is enriched including the drone point that is already destroyed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 13 15:59:00 2016 From: issues at jboss.org (Roger Wilco (JIRA)) Date: Wed, 13 Jan 2016 15:59:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2007) Weblogic JMX Deployment ignores server target In-Reply-To: References: Message-ID: Roger Wilco created ARQ-2007: -------------------------------- Summary: Weblogic JMX Deployment ignores server target Key: ARQ-2007 URL: https://issues.jboss.org/browse/ARQ-2007 Project: Arquillian Issue Type: Bug Components: WebLogic Containers Affects Versions: 1.0.1.Final Environment: WebLogic 12c (12.1.3, 12.2.1) Reporter: Roger Wilco Assignee: Vineet Reynolds Deploying to WebLogic server using the remote container module is performed through JMX. The DeploymentManager MBean API being used (deploy method) does not support deploy targets, which are defined in the Arquillian container configuration. i.e. deploy(name, applicationPath, plan) The application is then deployed to all managed servers even if the test is only executed on the specified target. For applications that execute initialization and deploy time operations this can cause severe problems when the application is started on multiple managed servers (e.g. admin server and a managed server). For applications that are not designed for non-clustered multiple server deployment, this prevents the ability to execute tests in an domain that has managed servers in addition to the admin server. The MBean has a second deploy method that takes a target parameter. i.e. deploy(name, applicationPath, targets, plan, deploymentOptions) If this method was used instead of the simple version then the application would be deployed to the specified server instead of all domain servers. If this was used then the application -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 14 07:39:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 14 Jan 2016 07:39:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2006) ISE for deployment-scoped drone point when manual deployment is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2006: -------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/57 > ISE for deployment-scoped drone point when manual deployment is used > -------------------------------------------------------------------- > > Key: ARQ-2006 > URL: https://issues.jboss.org/browse/ARQ-2006 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha5 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Beta1 > > > Consider these scenarios: > 1) > {code:java} > @Deployment(name = "first", managed = false) > public static Archive deployFirst() { > return ShrinkWrap.create(WebArchive.class); > } > @Deployment(name = "second") > public static WebArchive deploySecond() { > return ShrinkWrap.create(WebArchive.class); > } > @ArquillianResource > private Deployer deployer; > @Drone > @OperateOnDeployment("first") > private WebDriver firstBrowser; > @Drone > @OperateOnDeployment("second") > private WebDriver secondBrowser; > @Test > @InSequence(1) > public void runFirstTest() throws InterruptedException { > deployer.deploy("first"); > firstBrowser.get("http://google.com"); > deployer.undeploy("first"); > } > @Test > @InSequence(2) > public void runSecondTest() throws InterruptedException { > secondBrowser.get("http://google.com"); > } > {code} > 2) > {code:java} > @Deployment(name = "deployment", managed = false) > public static Archive deployFirst() { > return ShrinkWrap.create(WebArchive.class); > } > @ArquillianResource > private Deployer deployer; > @Drone > @OperateOnDeployment("deployment") > private WebDriver browser; > @Test > @InSequence(1) > public void runFirstTest() throws InterruptedException { > deployer.deploy("deployment"); > browser.get("http://google.com"); > deployer.undeploy("deployment"); > } > @Test > @InSequence(2) > public void runSecondTest() throws InterruptedException { > deployer.deploy("deployment"); > browser.get("http://google.com"); > deployer.undeploy("deployment"); > } > {code} > both of them lead to the IllegalStateException: > {noformat} > java.lang.IllegalStateException: Injection point DronePointImpl{droneClass=interface org.openqa.selenium.WebDriver, annotations=[@org.jboss.arquillian.drone.api.annotation.Drone(), @org.jboss.arquillian.container.test.api.OperateOnDeployment(value=deployment)], lifecycle=DEPLOYMENT} has deployment lifecycle and has to be prepared in @BeforeClass. > at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.ensureInjectionPointPrepared(DroneTestEnrichHelper.java:104) > at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.enrichTestClass(DroneTestEnrichHelper.java:72) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:54) > ... > {noformat} > The cause: the deployment-scoped drone point is destroyed before undeploy, but created only in BeforeClass. In the first test method the drone point is destroyed, however before the second test method is launched the test class is enriched including the drone point that is already destroyed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 14 07:39:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 14 Jan 2016 07:39:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2006) ISE for deployment-scoped drone point when manual deployment is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2006: -------------------------------- Status: Pull Request Sent (was: Open) > ISE for deployment-scoped drone point when manual deployment is used > -------------------------------------------------------------------- > > Key: ARQ-2006 > URL: https://issues.jboss.org/browse/ARQ-2006 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha5 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Beta1 > > > Consider these scenarios: > 1) > {code:java} > @Deployment(name = "first", managed = false) > public static Archive deployFirst() { > return ShrinkWrap.create(WebArchive.class); > } > @Deployment(name = "second") > public static WebArchive deploySecond() { > return ShrinkWrap.create(WebArchive.class); > } > @ArquillianResource > private Deployer deployer; > @Drone > @OperateOnDeployment("first") > private WebDriver firstBrowser; > @Drone > @OperateOnDeployment("second") > private WebDriver secondBrowser; > @Test > @InSequence(1) > public void runFirstTest() throws InterruptedException { > deployer.deploy("first"); > firstBrowser.get("http://google.com"); > deployer.undeploy("first"); > } > @Test > @InSequence(2) > public void runSecondTest() throws InterruptedException { > secondBrowser.get("http://google.com"); > } > {code} > 2) > {code:java} > @Deployment(name = "deployment", managed = false) > public static Archive deployFirst() { > return ShrinkWrap.create(WebArchive.class); > } > @ArquillianResource > private Deployer deployer; > @Drone > @OperateOnDeployment("deployment") > private WebDriver browser; > @Test > @InSequence(1) > public void runFirstTest() throws InterruptedException { > deployer.deploy("deployment"); > browser.get("http://google.com"); > deployer.undeploy("deployment"); > } > @Test > @InSequence(2) > public void runSecondTest() throws InterruptedException { > deployer.deploy("deployment"); > browser.get("http://google.com"); > deployer.undeploy("deployment"); > } > {code} > both of them lead to the IllegalStateException: > {noformat} > java.lang.IllegalStateException: Injection point DronePointImpl{droneClass=interface org.openqa.selenium.WebDriver, annotations=[@org.jboss.arquillian.drone.api.annotation.Drone(), @org.jboss.arquillian.container.test.api.OperateOnDeployment(value=deployment)], lifecycle=DEPLOYMENT} has deployment lifecycle and has to be prepared in @BeforeClass. > at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.ensureInjectionPointPrepared(DroneTestEnrichHelper.java:104) > at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.enrichTestClass(DroneTestEnrichHelper.java:72) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:54) > ... > {noformat} > The cause: the deployment-scoped drone point is destroyed before undeploy, but created only in BeforeClass. In the first test method the drone point is destroyed, however before the second test method is launched the test class is enriched including the drone point that is already destroyed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 10:26:00 2016 From: issues at jboss.org (Sanket Patel (JIRA)) Date: Mon, 18 Jan 2016 10:26:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: Sanket Patel created ARQ-2008: --------------------------------- Summary: Arquillian Key: ARQ-2008 URL: https://issues.jboss.org/browse/ARQ-2008 Project: Arquillian Issue Type: Feature Request Environment: I get the below errow when i try to run: I have also atttached my pom file import static org.junit.Assert.*; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.JavaArchive; import org.junit.Assert; import org.junit.Test; import org.junit.runner.RunWith; @RunWith(Arquillian.class) public class GreeterTest { @Deployment public static JavaArchive createDeployment() { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } @Test public void should_create_greeting() { assertEquals("sanket","sanket"); } } Reporter: Sanket Patel Attachments: pom.xml java.lang.NullPointerException at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) 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:204) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 10:29:00 2016 From: issues at jboss.org (Sanket Patel (JIRA)) Date: Mon, 18 Jan 2016 10:29:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Patel updated ARQ-2008: ------------------------------ Description: I get the below error when i try to run: I have also atttached my pom file import static org.junit.Assert.*; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.JavaArchive; import org.junit.Assert; import org.junit.Test; import org.junit.runner.RunWith; @RunWith(Arquillian.class) public class GreeterTest { @Deployment public static JavaArchive createDeployment() { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } @Test public void should_create_greeting() { assertEquals("sanket","sanket"); } } java.lang.NullPointerException at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) 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:204) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) was: java.lang.NullPointerException at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) 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:204) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: I get the below errow when i try to run: > I have also atttached my pom file > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() { > return ShrinkWrap.create(JavaArchive.class) > .addClass(Greeter.class) > .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); > } > @Test > public void should_create_greeting() { > assertEquals("sanket","sanket"); > } > } > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 10:29:00 2016 From: issues at jboss.org (Sanket Patel (JIRA)) Date: Mon, 18 Jan 2016 10:29:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Patel updated ARQ-2008: ------------------------------ Environment: Arquillian (was: I get the below errow when i try to run: I have also atttached my pom file import static org.junit.Assert.*; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.JavaArchive; import org.junit.Assert; import org.junit.Test; import org.junit.runner.RunWith; @RunWith(Arquillian.class) public class GreeterTest { @Deployment public static JavaArchive createDeployment() { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } @Test public void should_create_greeting() { assertEquals("sanket","sanket"); } }) > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 10:30:00 2016 From: issues at jboss.org (Sanket Patel (JIRA)) Date: Mon, 18 Jan 2016 10:30:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Patel updated ARQ-2008: ------------------------------ Description: I get the below error when i try to run: I have also atttached my pom file I am new and trying to learn Arquillian so forgive me if some major or useless mistake. import static org.junit.Assert.*; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.JavaArchive; import org.junit.Assert; import org.junit.Test; import org.junit.runner.RunWith; @RunWith(Arquillian.class) public class GreeterTest { @Deployment public static JavaArchive createDeployment() { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } @Test public void should_create_greeting() { assertEquals("sanket","sanket"); } } java.lang.NullPointerException at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) 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:204) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) was: I get the below error when i try to run: I have also atttached my pom file import static org.junit.Assert.*; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.JavaArchive; import org.junit.Assert; import org.junit.Test; import org.junit.runner.RunWith; @RunWith(Arquillian.class) public class GreeterTest { @Deployment public static JavaArchive createDeployment() { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } @Test public void should_create_greeting() { assertEquals("sanket","sanket"); } } java.lang.NullPointerException at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) 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:204) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 11:01:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 18 Jan 2016 11:01:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150102#comment-13150102 ] Aslak Knutsen commented on ARQ-2008: ------------------------------------ Hmm, I'm not able to reproduce this issue. Try refreshing/rebuilding the Maven project in Eclipse. Looks like it's missing some of the dependencies. I'm getting another issue from Weld tho, Weld 3 require a later version of CDI. Update to use jboss-javaee-7.0 instead of 6.0. > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 12:03:00 2016 From: issues at jboss.org (Sanket Patel (JIRA)) Date: Mon, 18 Jan 2016 12:03:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150151#comment-13150151 ] Sanket Patel commented on ARQ-2008: ----------------------------------- Hey, Thanks i made a new file and made changes and it works now. It works with glassfish though. I wanted to run it with wildfly. I have attached pom n you please help me making changes to that file so that i can use wildfly ? 4.0.0 org.jboss.arquillian.examples arquillian-persistence-tutorial 1.0.0-SNAPSHOT jar Arquillian Persistence Tutorial A self-contained Arquillian project for testing JPA 2 http://arquillian.org/guides/testing_java_persistence/ UTF-8 test maven-compiler-plugin 2.3.2 1.6 1.6 maven-surefire-plugin 2.12 org.jboss.arquillian arquillian-bom 1.0.3.Final import pom junit junit 4.8.1 test org.jboss.arquillian.junit arquillian-junit-container test arquillian-glassfish-embedded true org.jboss.arquillian.container arquillian-glassfish-embedded-3.1 1.0.0.CR3 test org.glassfish.main.extras glassfish-embedded-all 3.1.2 provided src/test/resources src/test/resources-glassfish-embedded maven-surefire-plugin 2.12 ${project.build.testOutputDirectory}/logging.properties ${project.build.directory}/derby.log arquillian-glassfish-remote org.jboss.spec jboss-javaee-web-6.0 3.0.0.Final pom provided xalan xalan org.jboss.arquillian.container arquillian-glassfish-remote-3.1 1.0.0.CR3 test src/test/resources src/test/resources-glassfish-remote arquillian-jbossas-managed org.jboss.spec jboss-javaee-web-6.0 3.0.0.Final pom provided xalan xalan org.jboss.as jboss-as-arquillian-container-managed 7.1.1.Final test org.jboss.arquillian.protocol arquillian-protocol-servlet test src/test/resources src/test/resources-jbossas-managed maven-dependency-plugin unpack process-test-classes unpack org.jboss.as jboss-as-dist 7.1.1.Final zip false target arquillian-jbossas-remote org.jboss.spec jboss-javaee-6.0 1.0.0.Final pom provided org.jboss.as jboss-as-arquillian-container-remote 7.1.1.Final test org.jboss.arquillian.protocol arquillian-protocol-servlet test src/test/resources src/test/resources-jbossas-managed > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 12:07:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 18 Jan 2016 12:07:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150154#comment-13150154 ] Aslak Knutsen commented on ARQ-2008: ------------------------------------ Have a look at Arquillian Chameleon; https://github.com/arquillian/arquillian-container-chameleon/ That should make it easier to setup. > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 12:08:00 2016 From: issues at jboss.org (Sanket Patel (JIRA)) Date: Mon, 18 Jan 2016 12:08:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150155#comment-13150155 ] Sanket Patel commented on ARQ-2008: ----------------------------------- Thank you i will check it out....! > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 12:30:00 2016 From: issues at jboss.org (Sanket Patel (JIRA)) Date: Mon, 18 Jan 2016 12:30:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150167#comment-13150167 ] Sanket Patel commented on ARQ-2008: ----------------------------------- Hey, The project you told i downloaded the zip and tried to run the same GreeterTest class mentioned above and got some errors. is there problem with the class ? java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:165) at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:102) at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:113) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:161) ... 9 more Caused by: java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.core.impl.ManagerImpl at org.jboss.arquillian.core.spi.SecurityActions.newInstance(SecurityActions.java:165) at org.jboss.arquillian.core.spi.SecurityActions.newInstance(SecurityActions.java:102) at org.jboss.arquillian.core.spi.ManagerBuilder.create(ManagerBuilder.java:77) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.(EventTestRunnerAdaptor.java:62) ... 14 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at org.jboss.arquillian.core.spi.SecurityActions.newInstance(SecurityActions.java:161) ... 17 more Caused by: java.lang.NoClassDefFoundError: org/jboss/arquillian/container/test/impl/enricher/resource/OperatesOnDeploymentAwareProvider at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at org.jboss.arquillian.protocol.servlet.ServletExtension.register(ServletExtension.java:40) at org.jboss.arquillian.core.impl.loadable.LoadableExtensionLoader.load(LoadableExtensionLoader.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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.ManagerImpl.fireProcessing(ManagerImpl.java:346) at org.jboss.arquillian.core.impl.ManagerImpl.(ManagerImpl.java:100) ... 22 more Caused by: java.lang.ClassNotFoundException: org.jboss.arquillian.container.test.impl.enricher.resource.OperatesOnDeploymentAwareProvider at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 47 more > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 12:33:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 18 Jan 2016 12:33:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150171#comment-13150171 ] Aslak Knutsen commented on ARQ-2008: ------------------------------------ What does your POM file look like now? > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 12:35:00 2016 From: issues at jboss.org (Sanket Patel (JIRA)) Date: Mon, 18 Jan 2016 12:35:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150175#comment-13150175 ] Sanket Patel commented on ARQ-2008: ----------------------------------- i just took the whole project from git so as to test that everthing in there works and then i can configure my pom file but that itself dosent work and gives me this error. > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 12:39:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 18 Jan 2016 12:39:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150177#comment-13150177 ] Aslak Knutsen commented on ARQ-2008: ------------------------------------ You copied your GreeterTest into the chameleon test folder and tried to compile/test it with no other changes, and you get that? > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 12:41:01 2016 From: issues at jboss.org (Sanket Patel (JIRA)) Date: Mon, 18 Jan 2016 12:41:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150179#comment-13150179 ] Sanket Patel commented on ARQ-2008: ----------------------------------- Yes that is truee...! > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 12:53:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 18 Jan 2016 12:53:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150184#comment-13150184 ] Aslak Knutsen commented on ARQ-2008: ------------------------------------ What happens when you run "mvn clean install" from command line? > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:02:00 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:02:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-423) Provide a way to intercept in some order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned ARQGRA-423: --------------------------------- Assignee: Juraj H?ska > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: 2.1.0.Alpha1 > > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-460) Introduce Graphene.log page extension, than enables to log to browser console (both, from Java and JavaScript code) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-460: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Introduce Graphene.log page extension, than enables to log to browser console (both, from Java and JavaScript code) > ------------------------------------------------------------------------------------------------------------------- > > Key: ARQGRA-460 > URL: https://issues.jboss.org/browse/ARQGRA-460 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > > Enable services like XHRInterceptor, RequestGuard and XHRHalter to log via Graphene.log. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-238) Catch client-side errors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-238: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Catch client-side errors > ------------------------ > > Key: ARQGRA-238 > URL: https://issues.jboss.org/browse/ARQGRA-238 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha2 > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > > Graphene should allow to inspect errors on client-side. > E.g. console.log output. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-364) Allow for extensibility of GrapheneElement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-364: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Allow for extensibility of GrapheneElement > ------------------------------------------ > > Key: ARQGRA-364 > URL: https://issues.jboss.org/browse/ARQGRA-364 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > > Implement GrapheneElement#as(Class type) method which will do a coercion to the given type. > If the given type is not implemented by wrapped WebElement, the service which implements this method will be called instead. This allows for simple extensibility mechanism: > {code} > @FindBy > GrapheneElement element; > @Test test() { > element.as(ValidableElement).checkValidity(); > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-417) Support for automatic scrolling to element before its usage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-417: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Support for automatic scrolling to element before its usage > ----------------------------------------------------------- > > Key: ARQGRA-417 > URL: https://issues.jboss.org/browse/ARQGRA-417 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > Priority: Minor > Fix For: 2.2-Tracking > > > It would be nice if Graphene supports automatic scrolling of browser window to {{WebElement}} / Page Fragment before its is used. > It can be useful for interactions with various popups web components: contextMenu, tooltip, ... > Those components can not be interacted correctly when they are not in the viewport, and thus one needs to scroll to them manually in his test. > It is often problem in CI environment, where tests run on screens with lower resolution (smaller part of the page fit the browser window, and lot of elements are not in the viewport). > My naive implementation of this would look like: > * intercept all calls to {{WebElements}} and PageFragments root elements > * in the interceptor method get the location of the element by: {{Point location = element.getLocation();}} > * a then scroll to it: {{jsExecutor.executeScript("window.scrollTo("" + location.getX() +", " + location.getY() + ")");}} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-390) Improve API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-390: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Improve API > ----------- > > Key: ARQGRA-390 > URL: https://issues.jboss.org/browse/ARQGRA-390 > Project: Arquillian Graphene > Issue Type: Epic > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-329) Add support for HTML5 form validation API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-329: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Add support for HTML5 form validation API > ----------------------------------------- > > Key: ARQGRA-329 > URL: https://issues.jboss.org/browse/ARQGRA-329 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Alpha4 > Reporter: Oliver Ki?? > Labels: padawan > Fix For: 2.2-Tracking > > > Add support for using HTML5 [form validation API|http://www.whatwg.org/specs/web-apps/current-work/#the-constraint-validation-api] from Graphene, {{checkValidity()}} method in particular. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-79) Migrate command interceptors to Selenium 2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-79: ----------------------------- Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Migrate command interceptors to Selenium 2 > ------------------------------------------ > > Key: ARQGRA-79 > URL: https://issues.jboss.org/browse/ARQGRA-79 > Project: Arquillian Graphene > Issue Type: Epic > Components: api, core > Reporter: Luk?? Fry? > Priority: Optional > Fix For: 2.2-Tracking > > > There is listener capability in Selenium 2, it could by used in place of interceptors from Ajocado 1. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-388) Use Proxy between the server and client to enhance Graphene's functionality In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-388: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Use Proxy between the server and client to enhance Graphene's functionality > --------------------------------------------------------------------------- > > Key: ARQGRA-388 > URL: https://issues.jboss.org/browse/ARQGRA-388 > Project: Arquillian Graphene > Issue Type: Epic > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-303) Improve failure messages in a fluent waiting API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-303: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Improve failure messages in a fluent waiting API > ------------------------------------------------ > > Key: ARQGRA-303 > URL: https://issues.jboss.org/browse/ARQGRA-303 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Luk?? Fry? > Priority: Minor > Fix For: 2.2-Tracking > > > Test can currently fail with this message: > {code} > org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for wrapped: text ('script executed') to be present in element found by By.tagName: title > {code} > We should: > * provide user with current value (last known value before the test failed) > * remove the "wrapped:" keyword, since it's misleading -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-318) Allow to select a code to execute based on a type of browser, its version, etc. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-318: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Allow to select a code to execute based on a type of browser, its version, etc. > ------------------------------------------------------------------------------- > > Key: ARQGRA-318 > URL: https://issues.jboss.org/browse/ARQGRA-318 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-389) Improve Usability In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-389: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Improve Usability > ----------------- > > Key: ARQGRA-389 > URL: https://issues.jboss.org/browse/ARQGRA-389 > Project: Arquillian Graphene > Issue Type: Epic > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:02 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:02 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-320) Allow to ask for element visibility without need to check its presence In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-320: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Allow to ask for element visibility without need to check its presence > ---------------------------------------------------------------------- > > Key: ARQGRA-320 > URL: https://issues.jboss.org/browse/ARQGRA-320 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: api, core, ftest > Affects Versions: 2.0.0.Alpha4 > Reporter: Juraj H?ska > Priority: Trivial > Fix For: 2.2-Tracking > > > Currently the only additional method of {{GrapheneElement}} is {{isPresent}}. > It would be nice to add {{isVisible}}. > It should be just matter of mixing {{isPresent}} and {{isDisplayed}} conditions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:02 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:02 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-377) Make Conditions API more concise when used for if statements and assertions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-377: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Make Conditions API more concise when used for if statements and assertions > --------------------------------------------------------------------------- > > Key: ARQGRA-377 > URL: https://issues.jboss.org/browse/ARQGRA-377 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.0.Beta1 > Reporter: Juraj H?ska > Fix For: 2.2-Tracking > > > Currently the conditions API looks like: > {code} > new WebElementConditionFactory(webElement).isEnabled().apply(webDriverInstance);{code} > It should be improved to be more concise. > Consider inspiring with *hamcrest* library ([link|https://code.google.com/p/hamcrest/]), which should allow to have conditions API like: > {code} > import static foo.bar.Matchers.*; > public void testEquals() { > WebElement element = browser.findBy(By.tagName("body")); > assertThat(element, isDisplayed()); > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:02 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:02 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-337) Disallow initialization of page abstractions which has non-private members In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-337: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Disallow initialization of page abstractions which has non-private members > -------------------------------------------------------------------------- > > Key: ARQGRA-337 > URL: https://issues.jboss.org/browse/ARQGRA-337 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > > It is not allowed to access Graphene-injected page abstractions directly through field references because then the object's calls can't be intercepted: > {code:java} > // not allowed > class Page { > @FindBy(...) > Tree tree; > } > {code} > The accessors should be used instead: > {code:java} > // allowed > class Page { > @FindBy(...) > private Tree tree; > public Tree tree() { > return tree; > } > } > {code} > We need to disallow that - either provide a warning or fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:02 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:02 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-226) graphene-webdriver-ftest cleanup for reference usage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-226: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > graphene-webdriver-ftest cleanup for reference usage > ---------------------------------------------------- > > Key: ARQGRA-226 > URL: https://issues.jboss.org/browse/ARQGRA-226 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Luk?? Fry? > Priority: Trivial > Fix For: 2.2-Tracking > > > {{graphene-webdriver-ftest}} should be used as reference usage for Graphene, thus we need to: > * remove dependency on {{arquillian-test-impl-base}} > * remove dependencies which are commented out > * add comments > ** on depchain - it brings all the dependencies > ** on arquillian-junit-standalone - explain what dependencies might be used instead {{arquillian-{testng,junit}-{standalone,container}}} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:02 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:02 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-135) Helpers for writing browser specific code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-135: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Helpers for writing browser specific code > ----------------------------------------- > > Key: ARQGRA-135 > URL: https://issues.jboss.org/browse/ARQGRA-135 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: api > Reporter: Luk?? Fry? > Priority: Minor > Fix For: 2.2-Tracking > > > Sometimes people need to deal with interoperability of the code between browsers. > It would be nice if Graphene 2 could provide nice way to handle that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:02 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:02 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-421) Graphene Interceptors: allow logging of invoked intercepted methods including interceptor chain In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-421: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Graphene Interceptors: allow logging of invoked intercepted methods including interceptor chain > ----------------------------------------------------------------------------------------------- > > Key: ARQGRA-421 > URL: https://issues.jboss.org/browse/ARQGRA-421 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:02 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:02 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-295) Provide more convenient way for Interceptors registration/unregistration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-295: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Provide more convenient way for Interceptors registration/unregistration > ------------------------------------------------------------------------- > > Key: ARQGRA-295 > URL: https://issues.jboss.org/browse/ARQGRA-295 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: api, core > Affects Versions: 2.0.0.Alpha4 > Reporter: Juraj H?ska > Priority: Minor > Fix For: 2.2-Tracking > > > It would be nice to have a more simple way of registering/unregistering Interceptors. > Currently this is supported: > {code} > GrapheneProxyInstance proxy = (GrapheneProxyInstance) webdriver; > proxy.registerInterceptor(new SearchContextInterceptor()); > {code} > It would be nice to have something like: > {code} > Graphene.registerInterceptor(new SearchContextInterceptor()); > {code} > It will be also good to choose class and method which will be intercepted. > The above mentioned is just minimum. > IMHO it would be awesome to provide way how to register interceptors like it is done in Java EE: > {code} > @Interceptor(MyCustomInterceptor.class) > public void testFooBar() { > ... > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:03 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:03 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-317) Automatic propagation of interceptors to child elements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-317: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Automatic propagation of interceptors to child elements > ------------------------------------------------------- > > Key: ARQGRA-317 > URL: https://issues.jboss.org/browse/ARQGRA-317 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:03 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:03 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-86) Support XHR Halter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-86: ----------------------------- Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Support XHR Halter > ------------------ > > Key: ARQGRA-86 > URL: https://issues.jboss.org/browse/ARQGRA-86 > Project: Arquillian Graphene > Issue Type: Epic > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:02 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:02 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-387) Improve Reporting got from Functional Tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-387: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Improve Reporting got from Functional Tests > ------------------------------------------- > > Key: ARQGRA-387 > URL: https://issues.jboss.org/browse/ARQGRA-387 > Project: Arquillian Graphene > Issue Type: Epic > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:03 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:03 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-313) Allow to inject unique page fragment from page without specifying root locator In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-313: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Allow to inject unique page fragment from page without specifying root locator > ------------------------------------------------------------------------------ > > Key: ARQGRA-313 > URL: https://issues.jboss.org/browse/ARQGRA-313 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > > The page fragment can contain instructions how to find itself in the given context: > {code:java} > @AutoFindBy(".rf-cal") > public class Calendar { > } > {code} > One can then inject such a page fragment without specifying locator: > {code:java} > @FindBy > Calendar calendar; > {code} > Note that the context of searching is dependent upon an injection point (where is page fragment being injected). > E.g.: > * whole page > * page fragment -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:03 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:03 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-331) Graphene guards fails when page stores reference to XMLHttpRequest before Graphene rewrites them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-331: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Graphene guards fails when page stores reference to XMLHttpRequest before Graphene rewrites them > ------------------------------------------------------------------------------------------------ > > Key: ARQGRA-331 > URL: https://issues.jboss.org/browse/ARQGRA-331 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.0.Alpha4 > Reporter: Oliver Ki?? > Assignee: Luk?? Fry? > Fix For: 2.2-Tracking > > > Graphene guards do not work correctly in the [AngularJS Kitchensink quickstart|https://github.com/jboss-jdf/jboss-as-quickstart/tree/master/kitchensink-angularjs]. > The registration form sends a XHR POST request on submit, but this is not recognized and clicking on the submit button with {{guardAjax(registerButton).click()}} throws an exception: "{{RequestGuardException: Request type 'XHR' was expected, but type 'NONE' was done instead}}". -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:03 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:03 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-439) Infer WebDriver context for @FindBy injections when there is only one qualified browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-439: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Infer WebDriver context for @FindBy injections when there is only one qualified browser > ---------------------------------------------------------------------------------------- > > Key: ARQGRA-439 > URL: https://issues.jboss.org/browse/ARQGRA-439 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core, ftest > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Fix For: 2.2-Tracking > > > When one is using qualified {{WebDriver}} instances, he needs to annotate also his {{WebElement}}, ... to distinguish in which context those elements should be resolved. > This has to be done also when there is only one (though qualified) browser injected. > Suppose: > {code} > @RunWith(Arquillian.class) > public class GrapheneBugDroneTest { > @Drone > @BugReport > WebDriver driver; > @Deployment(testable = false) > public static Archive deployHtml5DemoApp() { > return Deployments.createDeployment(); > } > @ArquillianResource > URL url; > @FindBy(id = "name") > @BugReport > WebElement nameField; > @Test > public void addUser() throws Exception { > driver.get(url.toString()); > Graphene.waitGui(driver).until().element(nameField).is().present(); > Assert.assertTrue(true); > } > @Qualifier > @Retention(RetentionPolicy.RUNTIME) > public static @interface BugReport { > } > } > {code} > Graphene can interfere which {{WebDriver}} instance was injected and act accordingly. The idea is also described [here|https://issues.jboss.org/browse/ARQGRA-435?focusedCommentId=12965697&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12965697]. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:03 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:03 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-64) Be able to find errors in resource loading In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-64: ----------------------------- Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Be able to find errors in resource loading > ------------------------------------------ > > Key: ARQGRA-64 > URL: https://issues.jboss.org/browse/ARQGRA-64 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Luk?? Fry? > Priority: Optional > Labels: investigative > Fix For: 2.2-Tracking > > > This can be achieved by watching {{console.log}} but just on certain browsers. > More integration would involve integration with browser. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:03 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:03 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-459) Allow to load Page Extensions from within WAR deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-459: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Allow to load Page Extensions from within WAR deployment > -------------------------------------------------------- > > Key: ARQGRA-459 > URL: https://issues.jboss.org/browse/ARQGRA-459 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Final > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > > Allows for debuggability -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:03 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:03 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-358) GrapheneContextImpl.getPageExtensionInstallatorProvider() returns null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-358: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > GrapheneContextImpl.getPageExtensionInstallatorProvider() returns null > ---------------------------------------------------------------------- > > Key: ARQGRA-358 > URL: https://issues.jboss.org/browse/ARQGRA-358 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Luk?? Fry? > Fix For: 2.2-Tracking > > > https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/context/GrapheneContextImpl.java#L96 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:04 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:04 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-326) Support for full initialization of outer class instance of a page fragment declared as inner class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-326: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Support for full initialization of outer class instance of a page fragment declared as inner class > -------------------------------------------------------------------------------------------------- > > Key: ARQGRA-326 > URL: https://issues.jboss.org/browse/ARQGRA-326 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Alpha4 > Reporter: Juraj H?ska > Priority: Minor > Fix For: 2.2-Tracking > > > If a Page Fragment is declared as inner class, then it can not access the fields of its outer class, as their are not inicialized by Graphene Enrichers, thus are {{null}}. > The possible ugly workaround for such initialization can be: > {code} > if (pageFragment.getClass().getEnclosingClass() != null) { > Field field = pageFragment.getClass().getDeclaredField("this$0"); > field.setAccessible(true); > Object outer = field.get(pageFragment); > enrichRecursively(root, outer); > } > {code} > It should be placed in some utility class, so it can be easily unit tested. > There is one drawback of this method and that is, the outer class can not contain injection point for the inner class, otherwise it will cycle. The inner class can be obtained only dynamically via {{Graphene.createPageFragment}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:04 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:04 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-301) Support for assertions on errors and console output In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-301: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Support for assertions on errors and console output > --------------------------------------------------- > > Key: ARQGRA-301 > URL: https://issues.jboss.org/browse/ARQGRA-301 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Brian Leathem > Fix For: 2.2-Tracking > > > In a recent Graphene based test [\[1\]|https://github.com/richfaces/components/commit/857f73bbf87f495e36c33072c5c4415d4b02be10#L1R85] I registered a window.onerror listener to store errors in the DOM for later retrieval by Graphene/Selenium for use in an assertion. > It would be great if Graphene could do this automatically, providing an API for accessing both error messages, and console output. > [1] https://github.com/richfaces/components/commit/857f73bbf87f495e36c33072c5c4415d4b02be10#L1R85 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:04 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:04 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-42) Reduce logging levels In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-42: ----------------------------- Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Reduce logging levels > --------------------- > > Key: ARQGRA-42 > URL: https://issues.jboss.org/browse/ARQGRA-42 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: junit, testng > Affects Versions: 1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Optional > Fix For: 2.2-Tracking > > > Ajocado outputs many debug information under INFO logging level. This level should be reduced to debug or even debug/fine. > It makes execution of the test slower and this information is not required until debugging. > It manifest namely with JUnit which redirects test output to console. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:04 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:04 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-221) Introduce own implementation of By to allow formatting (known from Graphene1) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-221: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Introduce own implementation of By to allow formatting (known from Graphene1) > ----------------------------------------------------------------------------- > > Key: ARQGRA-221 > URL: https://issues.jboss.org/browse/ARQGRA-221 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha2 > Reporter: Jan Papousek > Fix For: 2.2-Tracking > > > Locators in Graphene 1 contains #format(Object...) method which allows you to reuse in the following way: > {code} > JQueryLocator general = jq("div[id$=item{0}] td.rf-ac-itm-ico"); > for (int i=0; i<10; i++) { > JQueryLocator icon = general.format(1); > ... > } > {code} > It would be nice to have something similar in Graphene 2 (using By instead of JQueryLocator). > Other possibly usefel methods: > - getDescendant() > - getChild() -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:04 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:04 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-453) takeOnEveryAction acts only on methods from WebDriver object, add support for PO & PF & WebElement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-453: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > takeOnEveryAction acts only on methods from WebDriver object, add support for PO & PF & WebElement > -------------------------------------------------------------------------------------------------- > > Key: ARQGRA-453 > URL: https://issues.jboss.org/browse/ARQGRA-453 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core, screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: 2.2-Tracking > > > {{takeOnEveryAction}} now takes screenshot only when a method on {{WebDriver}} object is invoked. > To achieve something like visual testing, it would need to support also intercepting methods invoked on: > * {{WebElement}} > * Page objects > * Page fragments -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:10:04 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:10:04 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-434) Browser screenshooter acts only on @Default Drone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-434: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Browser screenshooter acts only on @Default Drone > ------------------------------------------------- > > Key: ARQGRA-434 > URL: https://issues.jboss.org/browse/ARQGRA-434 > Project: Arquillian Graphene > Issue Type: Bug > Components: screenshooter > Affects Versions: 2.1-Tracking > Reporter: Stefan Miklosovic > Assignee: Juraj H?ska > Fix For: 2.2-Tracking > > > Browser screenshooter acts only on Drone instances which do not have any qualifier but @Default since current implementation does this check: > {code} > GrapheneContext.getContextFor(Default.class) > {code} > This usage prevents user to use screenshooter in multibrowser scenarios like having Android browser and ordinary Firefox browser in one test class since they can (and must) be differentiated by additional qualifier put on @Drone instances. > Check should be done on instance level and not on qualifier level - meaning we should take context of Drone with ordinary (not mobile) browser which can have any qualifier possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:13:00 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:13:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-464) @Page injection should support parameter injection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned ARQGRA-464: --------------------------------- Assignee: (was: Karel Piwko) > @Page injection should support parameter injection > -------------------------------------------------- > > Key: ARQGRA-464 > URL: https://issues.jboss.org/browse/ARQGRA-464 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.1.0.Alpha1 > Reporter: Karel Piwko > Fix For: 2.1-Tracking > > > Graphene should support @Page injection even for parameter injection in test methods. This would make test case much more compact. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:13:00 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:13:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-380) Debugging in Eclipse throw InvocationException when inspecting fields enriched by Graphene In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned ARQGRA-380: --------------------------------- Assignee: (was: Juraj H?ska) > Debugging in Eclipse throw InvocationException when inspecting fields enriched by Graphene > ------------------------------------------------------------------------------------------ > > Key: ARQGRA-380 > URL: https://issues.jboss.org/browse/ARQGRA-380 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.0.Beta2 > Reporter: Juraj H?ska > Fix For: 2.1-Tracking > > > During debugging in Eclipse, when inspecting the values of the fields which are enriched by Graphene, an {{InvocationException}} is thrown. > We should investigate why it is so, and improve it if it is feasible. It can enhance the usability. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:15:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:15:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-353) Integration tests fail on Opera with Graphene Alpha5, Selenium 2.35 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-353: ------------------------------ Sprint: Graphene 2.0.0.CR2, Graphene 2.0.1 Sprint 1, Graphene 2.0.1, Graphene 2.0.2 (was: Graphene 2.0.0.CR2, Graphene 2.0.1 Sprint 1, Graphene 2.0.1) > Integration tests fail on Opera with Graphene Alpha5, Selenium 2.35 > ------------------------------------------------------------------- > > Key: ARQGRA-353 > URL: https://issues.jboss.org/browse/ARQGRA-353 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Luk?? Fry? > Priority: Optional > Labels: padawan > Fix For: 2.0-Tracking > > > {code} > Results : > Failed tests: testUnstable(org.jboss.arquillian.graphene.ftest.javascript.EnrichmentTestCase): Can't invoke unstable javascript extension: Can't invoke the javacript org.jboss.arquillian.graphene.ftest.javascript.EnrichmentTestCase$Unstable#simple() > testIncorrectInstallation(org.jboss.arquillian.graphene.ftest.page.extension.PageExtensionTestCase): Expected exception: java.lang.IllegalStateException > testJQuerySelectorCallingFindByDirectly(org.jboss.arquillian.graphene.ftest.page.extension.JQuerySelectorsPageExtensionTestCase): expected:<[h]1> but was:<[H]1> > testFindByOnWebElement(org.jboss.arquillian.graphene.ftest.page.extension.JQuerySelectorsPageExtensionTestCase): expected:<[h]1> but was:<[H]1> > testFindByOnListOfWebElement(org.jboss.arquillian.graphene.ftest.page.extension.JQuerySelectorsPageExtensionTestCase): expected:<[h]1> but was:<[H]1> > Tests in error: > testScreenMethods(org.jboss.arquillian.graphene.ftest.javascript.EnrichmentTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.javascript.EnrichmentTestCase$Screen#getHeight() > test(org.jboss.arquillian.graphene.ftest.javascript.TestCustomJSInterface): Can't invoke the javacript org.jboss.arquillian.graphene.page.document.Document#getTitle() > testWithSources(org.jboss.arquillian.graphene.ftest.javascript.JavaScriptPageExtensionTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.javascript.JavaScriptPageExtensionTestCase$HelloWorld#hello() > testWithInterfaceDependencies(org.jboss.arquillian.graphene.ftest.javascript.JavaScriptPageExtensionTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.javascript.JavaScriptPageExtensionTestCase$HelloWorld2#hello() > testStelenessAndJavascriptOnWebDriver(org.jboss.arquillian.graphene.ftest.webdriver.FindElementTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.webdriver.FindElementTestCase$JQueryInstallator#install() > testStelenessAndJavascriptOnWebElement(org.jboss.arquillian.graphene.ftest.webdriver.FindElementTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.webdriver.FindElementTestCase$JQueryInstallator#install() > testGuardHttp(org.jboss.arquillian.graphene.ftest.parallel.TestGrapheneUtilitiesParalelly): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardXhr(org.jboss.arquillian.graphene.ftest.parallel.TestGrapheneUtilitiesParalelly): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardHttp(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardAjax(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardDelayedAjax(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardDelayedAjaxProcessing(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardDelayedTrigerringAndProcessing(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardDelayedAjaxProcessingWithCodeArgument(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardAjaxWithRelocation(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardHttpFailure(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Unexpected exception, expected but was > testGuardNoRequestFailure(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Unexpected exception, expected but was > testGuardAjaxFailure(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Unexpected exception, expected but was > testDelayedGuardNoRequest(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Unexpected exception, expected but was > testGuardNoRequest(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testXhr(org.jboss.arquillian.graphene.ftest.guard.RequestGuardTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#getRequestType() > testHttp(org.jboss.arquillian.graphene.ftest.guard.RequestGuardTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#getRequestType() > testCorrectInstallation(org.jboss.arquillian.graphene.ftest.page.extension.PageExtensionTestCase): com.opera.core.systems.scope.exceptions.ResponseNotReceivedException: No response in a timely fashion > testDeletion(org.jboss.arquillian.graphene.ftest.enricher.TestHandlingOfStaleElements): com.sun.proxy.$Proxy21 cannot be cast to com.opera.core.systems.OperaWebElement > testReplacement(org.jboss.arquillian.graphene.ftest.enricher.TestHandlingOfStaleElements): com.sun.proxy.$Proxy21 cannot be cast to com.opera.core.systems.OperaWebElement > testOneWithJavascript(org.jboss.arquillian.graphene.ftest.enricher.TestGrapheneElement): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.enricher.TestGrapheneElement$TestJavascript#getInnerHtml() > testListWithJavascript(org.jboss.arquillian.graphene.ftest.enricher.TestGrapheneElement): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.enricher.TestGrapheneElement$TestJavascript#getInnerHtml() > Tests run: 271, Failures: 5, Errors: 27, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:15:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:15:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-395) Graphene.guardAjax() doesn't work correctly in IE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-395: ------------------------------ Sprint: Graphene 2.0.1, Graphene 2.0.2 (was: Graphene 2.0.1) > Graphene.guardAjax() doesn't work correctly in IE > ------------------------------------------------- > > Key: ARQGRA-395 > URL: https://issues.jboss.org/browse/ARQGRA-395 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.0.CR2 > Environment: IE 7, 8, 9 > Reporter: Jan Dosoudil > Fix For: 2.0-Tracking > > > I have jsf page h:commandButton with f:ajax. Testing with Graphene.guardAjax(button).click(); works with Firefox, htmlUnit, phantomjs but doesn't with Internet Explorer (7, 8, 9). Internet explorer calls onclick function but without return false which causes full page submit. > button.click() works ok. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:15:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:15:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-407) Document WebDriverWait API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-407: ------------------------------ Sprint: Graphene 2.0.1, Graphene 2.0.2 (was: Graphene 2.0.1) > Document WebDriverWait API > -------------------------- > > Key: ARQGRA-407 > URL: https://issues.jboss.org/browse/ARQGRA-407 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Luk?? Fry? > Priority: Critical > Fix For: 2.0-Tracking > > > https://github.com/arquillian/arquillian-graphene/blob/2.0.0.Final/api/src/main/java/org/jboss/arquillian/graphene/wait/WebDriverWait.java#L45 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:15:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:15:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-407) Document WebDriverWait API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-407: ------------------------------ Sprint: Graphene 2.0.1 (was: Graphene 2.0.1, Graphene 2.0.2) > Document WebDriverWait API > -------------------------- > > Key: ARQGRA-407 > URL: https://issues.jboss.org/browse/ARQGRA-407 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Luk?? Fry? > Priority: Critical > Fix For: 2.0-Tracking > > > https://github.com/arquillian/arquillian-graphene/blob/2.0.0.Final/api/src/main/java/org/jboss/arquillian/graphene/wait/WebDriverWait.java#L45 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:15:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:15:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-396) Check/review JDF web-UI quickstarts for Graphene reference usage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-396: ------------------------------ Sprint: Graphene 2.0.1 Sprint 1 (was: Graphene 2.0.1 Sprint 1, Graphene 2.0.2) > Check/review JDF web-UI quickstarts for Graphene reference usage > ---------------------------------------------------------------- > > Key: ARQGRA-396 > URL: https://issues.jboss.org/browse/ARQGRA-396 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Luk?? Fry? > Assignee: Oliver Ki?? > Fix For: 2.0-Tracking > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:15:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:15:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-395) Graphene.guardAjax() doesn't work correctly in IE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-395: ------------------------------ Sprint: Graphene 2.0.1 (was: Graphene 2.0.1, Graphene 2.0.2) > Graphene.guardAjax() doesn't work correctly in IE > ------------------------------------------------- > > Key: ARQGRA-395 > URL: https://issues.jboss.org/browse/ARQGRA-395 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.0.CR2 > Environment: IE 7, 8, 9 > Reporter: Jan Dosoudil > Fix For: 2.0-Tracking > > > I have jsf page h:commandButton with f:ajax. Testing with Graphene.guardAjax(button).click(); works with Firefox, htmlUnit, phantomjs but doesn't with Internet Explorer (7, 8, 9). Internet explorer calls onclick function but without return false which causes full page submit. > button.click() works ok. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:15:01 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:15:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-353) Integration tests fail on Opera with Graphene Alpha5, Selenium 2.35 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-353: ------------------------------ Sprint: Graphene 2.0.0.CR2, Graphene 2.0.1 Sprint 1, Graphene 2.0.1 (was: Graphene 2.0.0.CR2, Graphene 2.0.1 Sprint 1, Graphene 2.0.1, Graphene 2.0.2) > Integration tests fail on Opera with Graphene Alpha5, Selenium 2.35 > ------------------------------------------------------------------- > > Key: ARQGRA-353 > URL: https://issues.jboss.org/browse/ARQGRA-353 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Luk?? Fry? > Priority: Optional > Labels: padawan > Fix For: 2.0-Tracking > > > {code} > Results : > Failed tests: testUnstable(org.jboss.arquillian.graphene.ftest.javascript.EnrichmentTestCase): Can't invoke unstable javascript extension: Can't invoke the javacript org.jboss.arquillian.graphene.ftest.javascript.EnrichmentTestCase$Unstable#simple() > testIncorrectInstallation(org.jboss.arquillian.graphene.ftest.page.extension.PageExtensionTestCase): Expected exception: java.lang.IllegalStateException > testJQuerySelectorCallingFindByDirectly(org.jboss.arquillian.graphene.ftest.page.extension.JQuerySelectorsPageExtensionTestCase): expected:<[h]1> but was:<[H]1> > testFindByOnWebElement(org.jboss.arquillian.graphene.ftest.page.extension.JQuerySelectorsPageExtensionTestCase): expected:<[h]1> but was:<[H]1> > testFindByOnListOfWebElement(org.jboss.arquillian.graphene.ftest.page.extension.JQuerySelectorsPageExtensionTestCase): expected:<[h]1> but was:<[H]1> > Tests in error: > testScreenMethods(org.jboss.arquillian.graphene.ftest.javascript.EnrichmentTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.javascript.EnrichmentTestCase$Screen#getHeight() > test(org.jboss.arquillian.graphene.ftest.javascript.TestCustomJSInterface): Can't invoke the javacript org.jboss.arquillian.graphene.page.document.Document#getTitle() > testWithSources(org.jboss.arquillian.graphene.ftest.javascript.JavaScriptPageExtensionTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.javascript.JavaScriptPageExtensionTestCase$HelloWorld#hello() > testWithInterfaceDependencies(org.jboss.arquillian.graphene.ftest.javascript.JavaScriptPageExtensionTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.javascript.JavaScriptPageExtensionTestCase$HelloWorld2#hello() > testStelenessAndJavascriptOnWebDriver(org.jboss.arquillian.graphene.ftest.webdriver.FindElementTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.webdriver.FindElementTestCase$JQueryInstallator#install() > testStelenessAndJavascriptOnWebElement(org.jboss.arquillian.graphene.ftest.webdriver.FindElementTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.webdriver.FindElementTestCase$JQueryInstallator#install() > testGuardHttp(org.jboss.arquillian.graphene.ftest.parallel.TestGrapheneUtilitiesParalelly): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardXhr(org.jboss.arquillian.graphene.ftest.parallel.TestGrapheneUtilitiesParalelly): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardHttp(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardAjax(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardDelayedAjax(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardDelayedAjaxProcessing(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardDelayedTrigerringAndProcessing(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardDelayedAjaxProcessingWithCodeArgument(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardAjaxWithRelocation(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testGuardHttpFailure(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Unexpected exception, expected but was > testGuardNoRequestFailure(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Unexpected exception, expected but was > testGuardAjaxFailure(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Unexpected exception, expected but was > testDelayedGuardNoRequest(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Unexpected exception, expected but was > testGuardNoRequest(org.jboss.arquillian.graphene.ftest.guard.GuardsTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > testXhr(org.jboss.arquillian.graphene.ftest.guard.RequestGuardTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#getRequestType() > testHttp(org.jboss.arquillian.graphene.ftest.guard.RequestGuardTestCase): Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#getRequestType() > testCorrectInstallation(org.jboss.arquillian.graphene.ftest.page.extension.PageExtensionTestCase): com.opera.core.systems.scope.exceptions.ResponseNotReceivedException: No response in a timely fashion > testDeletion(org.jboss.arquillian.graphene.ftest.enricher.TestHandlingOfStaleElements): com.sun.proxy.$Proxy21 cannot be cast to com.opera.core.systems.OperaWebElement > testReplacement(org.jboss.arquillian.graphene.ftest.enricher.TestHandlingOfStaleElements): com.sun.proxy.$Proxy21 cannot be cast to com.opera.core.systems.OperaWebElement > testOneWithJavascript(org.jboss.arquillian.graphene.ftest.enricher.TestGrapheneElement): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.enricher.TestGrapheneElement$TestJavascript#getInnerHtml() > testListWithJavascript(org.jboss.arquillian.graphene.ftest.enricher.TestGrapheneElement): Can't invoke the javacript org.jboss.arquillian.graphene.ftest.enricher.TestGrapheneElement$TestJavascript#getInnerHtml() > Tests run: 271, Failures: 5, Errors: 27, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 04:22:00 2016 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 19 Jan 2016 04:22:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-462) Polish AjaxHalter API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned ARQGRA-462: --------------------------------- Assignee: Luk?? Fry? > Polish AjaxHalter API > --------------------- > > Key: ARQGRA-462 > URL: https://issues.jboss.org/browse/ARQGRA-462 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: api, core > Affects Versions: 2.1.0.Alpha2 > Reporter: Juraj H?ska > Assignee: Luk?? Fry? > Fix For: 2.1-Tracking > > > The API for {{AjaxHalter}} was ported from {{XHRHalter}} in _Graphene1_. > We talked about polishing it based on the community feedback after releasing {{2.1.0.Alpha2}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 16:26:00 2016 From: issues at jboss.org (Sanket Patel (JIRA)) Date: Tue, 19 Jan 2016 16:26:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Patel resolved ARQ-2008. ------------------------------- Resolution: Done > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 16:27:00 2016 From: issues at jboss.org (Sanket Patel (JIRA)) Date: Tue, 19 Jan 2016 16:27:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2008) Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150927#comment-13150927 ] Sanket Patel commented on ARQ-2008: ----------------------------------- Hey thanks for the help. I resolved the issue. There was version problems > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > 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:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 05:45:01 2016 From: issues at jboss.org (Grzegorz Grzybek (JIRA)) Date: Mon, 25 Jan 2016 05:45:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1940) arquillian-osgi-bundle is not undeployed when executing a test with surefire 2.18 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152930#comment-13152930 ] Grzegorz Grzybek commented on ARQ-1940: --------------------------------------- I've just checked that it works well with surefure-plugin 2.19.1. > arquillian-osgi-bundle is not undeployed when executing a test with surefire 2.18 > --------------------------------------------------------------------------------- > > Key: ARQ-1940 > URL: https://issues.jboss.org/browse/ARQ-1940 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Tomas Rohovsky > Priority: Minor > Attachments: surefire-reproducer.zip > > > arquillian-osgi-bundle is not undeployed when executing a test with surefire-plugin 2.18. It works with older versions of surefire-plugin. A reproducer is attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 05:45:01 2016 From: issues at jboss.org (Grzegorz Grzybek (JIRA)) Date: Mon, 25 Jan 2016 05:45:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1940) arquillian-osgi-bundle is not undeployed when executing a test with surefire 2.18 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152930#comment-13152930 ] Grzegorz Grzybek edited comment on ARQ-1940 at 1/25/16 5:44 AM: ---------------------------------------------------------------- I've just checked that it works well with surefure-plugin 2.19.1. [~trohovsky]. I think you could close this issue. was (Author: grgrzybek): I've just checked that it works well with surefure-plugin 2.19.1. > arquillian-osgi-bundle is not undeployed when executing a test with surefire 2.18 > --------------------------------------------------------------------------------- > > Key: ARQ-1940 > URL: https://issues.jboss.org/browse/ARQ-1940 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Tomas Rohovsky > Priority: Minor > Attachments: surefire-reproducer.zip > > > arquillian-osgi-bundle is not undeployed when executing a test with surefire-plugin 2.18. It works with older versions of surefire-plugin. A reproducer is attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 09:31:00 2016 From: issues at jboss.org (Tomas Rohovsky (JIRA)) Date: Mon, 25 Jan 2016 09:31:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1940) arquillian-osgi-bundle is not undeployed when executing a test with surefire 2.18 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Rohovsky resolved ARQ-1940. --------------------------------- Resolution: Resolved at Apache Indeed, arquillian-osgi-bundle is undeployed when using surefire 2.19.1. [~tibor17] and [~grgrzybek] thanks for taking care of this issue. > arquillian-osgi-bundle is not undeployed when executing a test with surefire 2.18 > --------------------------------------------------------------------------------- > > Key: ARQ-1940 > URL: https://issues.jboss.org/browse/ARQ-1940 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Tomas Rohovsky > Priority: Minor > Attachments: surefire-reproducer.zip > > > arquillian-osgi-bundle is not undeployed when executing a test with surefire-plugin 2.18. It works with older versions of surefire-plugin. A reproducer is attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 10:42:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 10:42:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2009) ServletProtocol depend on Servlet 3.0 In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-2009: ---------------------------------- Summary: ServletProtocol depend on Servlet 3.0 Key: ARQ-2009 URL: https://issues.jboss.org/browse/ARQ-2009 Project: Arquillian Issue Type: Bug Components: Test Protocol SPIs and Implementation Affects Versions: 1.1.10.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 11:19:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 11:19:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2009) ServletProtocol depend on Servlet 3.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-2009: ------------------------------- Fix Version/s: 1.1.11.Final > ServletProtocol depend on Servlet 3.0 > ------------------------------------- > > Key: ARQ-2009 > URL: https://issues.jboss.org/browse/ARQ-2009 > Project: Arquillian > Issue Type: Bug > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.10.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 11:20:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 11:20:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2009) ServletProtocol depend on Servlet 3.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-2009. -------------------------------- Resolution: Done > ServletProtocol depend on Servlet 3.0 > ------------------------------------- > > Key: ARQ-2009 > URL: https://issues.jboss.org/browse/ARQ-2009 > Project: Arquillian > Issue Type: Bug > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.10.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 11:20:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 11:20:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1996) Upgrade to ShrinkWrap 1.2.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1996: ------------------------------- Fix Version/s: 1.1.11.Final (was: 1.2.0.Alpha1) > Upgrade to ShrinkWrap 1.2.3 > --------------------------- > > Key: ARQ-1996 > URL: https://issues.jboss.org/browse/ARQ-1996 > Project: Arquillian > Issue Type: Component Upgrade > Components: Base Implementation > Affects Versions: 1.1.10.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 11:23:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 11:23:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2010) Report first Exception caught in TestRunner In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-2010: ---------------------------------- Summary: Report first Exception caught in TestRunner Key: ARQ-2010 URL: https://issues.jboss.org/browse/ARQ-2010 Project: Arquillian Issue Type: Enhancement Components: Test Protocol SPIs and Implementation Affects Versions: 1.1.10.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.1.11.Final In particular when testing with the Arquillian Persistence extension it can be very difficult to diagnose problems in a test: Usually when seeding of the database fails some other After event listener fails as well, e.g. evaluation of @ShouldMatchDataSet. Then Arquillian only reports the last error that the actual result differs from the expected one. This makes fixing the test very hard. This PR changes the JUnitTestRunner so that it keeps the first exception that passes by ExpectedExceptionHolder.testFailure() instead of the last one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 11:26:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 11:26:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2010) Report first Exception caught in TestRunner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-2010: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/97 > Report first Exception caught in TestRunner > ------------------------------------------- > > Key: ARQ-2010 > URL: https://issues.jboss.org/browse/ARQ-2010 > Project: Arquillian > Issue Type: Enhancement > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.10.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > > In particular when testing with the Arquillian Persistence extension it can be very difficult to diagnose problems in a test: > Usually when seeding of the database fails some other After event listener fails as well, e.g. evaluation of @ShouldMatchDataSet. > Then Arquillian only reports the last error that the actual result differs from the expected one. > This makes fixing the test very hard. > This PR changes the JUnitTestRunner so that it keeps the first exception that passes by ExpectedExceptionHolder.testFailure() instead of the last one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 11:27:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 11:27:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2010) Report first Exception caught in TestRunner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-2010: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Report first Exception caught in TestRunner > ------------------------------------------- > > Key: ARQ-2010 > URL: https://issues.jboss.org/browse/ARQ-2010 > Project: Arquillian > Issue Type: Enhancement > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.10.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > > In particular when testing with the Arquillian Persistence extension it can be very difficult to diagnose problems in a test: > Usually when seeding of the database fails some other After event listener fails as well, e.g. evaluation of @ShouldMatchDataSet. > Then Arquillian only reports the last error that the actual result differs from the expected one. > This makes fixing the test very hard. > This PR changes the JUnitTestRunner so that it keeps the first exception that passes by ExpectedExceptionHolder.testFailure() instead of the last one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 11:33:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 11:33:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1954) Support @Rule enrichement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1954: ------------------------------- Fix Version/s: 1.1.11.Final > Support @Rule enrichement > ------------------------- > > Key: ARQ-1954 > URL: https://issues.jboss.org/browse/ARQ-1954 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.8.Final > Reporter: Karel Piwko > Fix For: 1.1.11.Final > > > Arquillian should by default enrich JUnit @Rule statements. > Similarly to https://github.com/aerogear/aerogear-testing-tools/blob/master/arquillian-rule/src/test/java/org/jboss/aerogear/arquillian/junit/RuleInjectionTest.java -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 11:33:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 11:33:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1954) Support @Rule enrichement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1954: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/85 > Support @Rule enrichement > ------------------------- > > Key: ARQ-1954 > URL: https://issues.jboss.org/browse/ARQ-1954 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.8.Final > Reporter: Karel Piwko > Fix For: 1.1.11.Final > > > Arquillian should by default enrich JUnit @Rule statements. > Similarly to https://github.com/aerogear/aerogear-testing-tools/blob/master/arquillian-rule/src/test/java/org/jboss/aerogear/arquillian/junit/RuleInjectionTest.java -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 11:34:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 11:34:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1954) Support @Rule enrichement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1954: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support @Rule enrichement > ------------------------- > > Key: ARQ-1954 > URL: https://issues.jboss.org/browse/ARQ-1954 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.8.Final > Reporter: Karel Piwko > Fix For: 1.1.11.Final > > > Arquillian should by default enrich JUnit @Rule statements. > Similarly to https://github.com/aerogear/aerogear-testing-tools/blob/master/arquillian-rule/src/test/java/org/jboss/aerogear/arquillian/junit/RuleInjectionTest.java -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 12:07:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 12:07:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1956) Add Instance to Before|AfterEnrichment events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1956: ------------------------------- Fix Version/s: 1.1.11.Final (was: 1.2.0.Alpha1) > Add Instance to Before|AfterEnrichment events > --------------------------------------------- > > Key: ARQ-1956 > URL: https://issues.jboss.org/browse/ARQ-1956 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.8.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 12:08:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 12:08:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1956) Add Instance to Before|AfterEnrichment events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1956. ------------------------------ Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/8bf22a55c88b89284d5c62d5b31a8c06ff243c24 > Add Instance to Before|AfterEnrichment events > --------------------------------------------- > > Key: ARQ-1956 > URL: https://issues.jboss.org/browse/ARQ-1956 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.8.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 12:12:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 12:12:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1937) Class loading issue with injected deployer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1937: ------------------------------- Fix Version/s: 1.1.11.Final (was: 1.2.0.Alpha1) > Class loading issue with injected deployer > ------------------------------------------- > > Key: ARQ-1937 > URL: https://issues.jboss.org/browse/ARQ-1937 > Project: Arquillian > Issue Type: Bug > Components: Deployable Containers SPI > Affects Versions: 1.1.1.Final > Reporter: Martin Gencur > Fix For: 1.1.11.Final > > > Steps to reproduce: > 1) inject a Deployer via @ArquillianResource > 2) declare a deployment as managed=false, use the deployer to deploy artifacts to a managed container > 3) run a test method that operates on the deployment > 4) check that classes inside the test method have the same classloader as the test class itself (see the code below where I call cache.getClass().getClassLoader()) > 5) this does not happen when the deployment is managed=true and deployer API is NOT used. In this case, the classes have a different class loader > In the test below, I tried to load different versions of Infinispan in two deployments and test backward compatibility. However, due to this class loading issue the Infinispan classes are of the latest version regardless of libraries bundled in the WAR. This is probably due to the fact that the Maven test module has the latest Infinispan libraries defined in while the older version is downloaded separately via Maven dependency plugin. > {code} > package com.jboss.datagrid.test.backwardcompatibility; > @RunWith(Arquillian.class) > public class SingleFileStoreBackwardCompatibilityIT { > private DefaultCacheManager dfc; > private String cacheName = "testCache"; > private static final String OLD_ISPN = "dep1_with_old_ispn"; > private static final String NEW_ISPN = "dep2_with_new_ispn"; > private static Map storedMap; > @ArquillianResource > Deployer deployer; > @Deployment(name = OLD_ISPN, testable = true, managed = true, order=1) > @TargetsContainer("container1") > public static WebArchive createDeploymentOld() { > WebArchive jar = DeploymentBuilder.createTestArchiveWithPreviousJDG("test1.war", "previous"); > System.out.println("ClassLoader: " + SingleFileStoreBackwardCompatibilityIT.class.getClassLoader()); > return jar; > } > @Deployment(name = NEW_ISPN, testable = true, managed = true, order=2) > @TargetsContainer("container2") > public static WebArchive createDeploymentNew() { > WebArchive jar = DeploymentBuilder.createTestArchive("test2.war", "current"); > return jar; > } > private DefaultCacheManager configureCacheManager(boolean clearCacheStore) throws Exception { > GlobalConfiguration glob = new GlobalConfigurationBuilder().nonClusteredDefault() > .globalJmxStatistics().allowDuplicateDomains(true). > build(); > ConfigurationBuilder c = new ConfigurationBuilder(); > c.clustering().cacheMode(CacheMode.LOCAL); > File tmpStore = new File("/tmp/cache/" + cacheName + ".dat"); > if (clearCacheStore && tmpStore.exists()) { > tmpStore.delete(); > } > c.persistence().passivation(false).addSingleFileStore().purgeOnStartup(false).location("/tmp/cache/"); > Configuration cnf = c.build(); > DefaultCacheManager manager = new DefaultCacheManager(glob); > manager.defineConfiguration(cacheName, cnf); > return manager; > } > @Test > @OperateOnDeployment(OLD_ISPN) > @InSequence(1) > public void testStoreWithOldJDG() throws Exception { > deployer.deploy(OLD_ISPN); > dfc = configureCacheManager(true); > dfc.start(); > Cache cache = dfc.getCache(cacheName); > System.out.println("Version: " + cache.getVersion()); > System.out.println("ClassLoader: " + cache.getClass().getClassLoader()); > storedMap = new HashMap(); > storedMap.put("k", "v"); > cache.put("mapKey", storedMap); > dfc.stop(); > deployer.undeploy(OLD_ISPN); > } > @Test > @OperateOnDeployment(NEW_ISPN) > @InSequence(2) > public void testReadWithNewJDG() throws Exception { > deployer.deploy(NEW_ISPN); > dfc = configureCacheManager(false); > dfc.start(); > Cache cache = dfc.getCache(cacheName); > System.out.println("ClassLoader: " + cache.getClass().getClassLoader()); > System.out.println("Version: " + cache.getVersion()); > assertEquals(storedMap, cache.get("mapKey")); > dfc.stop(); > deployer.undeploy(NEW_ISPN); > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 12:13:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 12:13:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1937) Class loading issue with injected deployer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1937: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/83 > Class loading issue with injected deployer > ------------------------------------------- > > Key: ARQ-1937 > URL: https://issues.jboss.org/browse/ARQ-1937 > Project: Arquillian > Issue Type: Bug > Components: Deployable Containers SPI > Affects Versions: 1.1.1.Final > Reporter: Martin Gencur > Fix For: 1.1.11.Final > > > Steps to reproduce: > 1) inject a Deployer via @ArquillianResource > 2) declare a deployment as managed=false, use the deployer to deploy artifacts to a managed container > 3) run a test method that operates on the deployment > 4) check that classes inside the test method have the same classloader as the test class itself (see the code below where I call cache.getClass().getClassLoader()) > 5) this does not happen when the deployment is managed=true and deployer API is NOT used. In this case, the classes have a different class loader > In the test below, I tried to load different versions of Infinispan in two deployments and test backward compatibility. However, due to this class loading issue the Infinispan classes are of the latest version regardless of libraries bundled in the WAR. This is probably due to the fact that the Maven test module has the latest Infinispan libraries defined in while the older version is downloaded separately via Maven dependency plugin. > {code} > package com.jboss.datagrid.test.backwardcompatibility; > @RunWith(Arquillian.class) > public class SingleFileStoreBackwardCompatibilityIT { > private DefaultCacheManager dfc; > private String cacheName = "testCache"; > private static final String OLD_ISPN = "dep1_with_old_ispn"; > private static final String NEW_ISPN = "dep2_with_new_ispn"; > private static Map storedMap; > @ArquillianResource > Deployer deployer; > @Deployment(name = OLD_ISPN, testable = true, managed = true, order=1) > @TargetsContainer("container1") > public static WebArchive createDeploymentOld() { > WebArchive jar = DeploymentBuilder.createTestArchiveWithPreviousJDG("test1.war", "previous"); > System.out.println("ClassLoader: " + SingleFileStoreBackwardCompatibilityIT.class.getClassLoader()); > return jar; > } > @Deployment(name = NEW_ISPN, testable = true, managed = true, order=2) > @TargetsContainer("container2") > public static WebArchive createDeploymentNew() { > WebArchive jar = DeploymentBuilder.createTestArchive("test2.war", "current"); > return jar; > } > private DefaultCacheManager configureCacheManager(boolean clearCacheStore) throws Exception { > GlobalConfiguration glob = new GlobalConfigurationBuilder().nonClusteredDefault() > .globalJmxStatistics().allowDuplicateDomains(true). > build(); > ConfigurationBuilder c = new ConfigurationBuilder(); > c.clustering().cacheMode(CacheMode.LOCAL); > File tmpStore = new File("/tmp/cache/" + cacheName + ".dat"); > if (clearCacheStore && tmpStore.exists()) { > tmpStore.delete(); > } > c.persistence().passivation(false).addSingleFileStore().purgeOnStartup(false).location("/tmp/cache/"); > Configuration cnf = c.build(); > DefaultCacheManager manager = new DefaultCacheManager(glob); > manager.defineConfiguration(cacheName, cnf); > return manager; > } > @Test > @OperateOnDeployment(OLD_ISPN) > @InSequence(1) > public void testStoreWithOldJDG() throws Exception { > deployer.deploy(OLD_ISPN); > dfc = configureCacheManager(true); > dfc.start(); > Cache cache = dfc.getCache(cacheName); > System.out.println("Version: " + cache.getVersion()); > System.out.println("ClassLoader: " + cache.getClass().getClassLoader()); > storedMap = new HashMap(); > storedMap.put("k", "v"); > cache.put("mapKey", storedMap); > dfc.stop(); > deployer.undeploy(OLD_ISPN); > } > @Test > @OperateOnDeployment(NEW_ISPN) > @InSequence(2) > public void testReadWithNewJDG() throws Exception { > deployer.deploy(NEW_ISPN); > dfc = configureCacheManager(false); > dfc.start(); > Cache cache = dfc.getCache(cacheName); > System.out.println("ClassLoader: " + cache.getClass().getClassLoader()); > System.out.println("Version: " + cache.getVersion()); > assertEquals(storedMap, cache.get("mapKey")); > dfc.stop(); > deployer.undeploy(NEW_ISPN); > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 12:19:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 12:19:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1937) Class loading issue with injected deployer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1937: ------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Aslak Knutsen Resolution: Done Pushed upstream https://github.com/arquillian/arquillian-core/commit/96ad96f345e06c11e04eef94d0a3b4f5f23f684c > Class loading issue with injected deployer > ------------------------------------------- > > Key: ARQ-1937 > URL: https://issues.jboss.org/browse/ARQ-1937 > Project: Arquillian > Issue Type: Bug > Components: Deployable Containers SPI > Affects Versions: 1.1.1.Final > Reporter: Martin Gencur > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > > Steps to reproduce: > 1) inject a Deployer via @ArquillianResource > 2) declare a deployment as managed=false, use the deployer to deploy artifacts to a managed container > 3) run a test method that operates on the deployment > 4) check that classes inside the test method have the same classloader as the test class itself (see the code below where I call cache.getClass().getClassLoader()) > 5) this does not happen when the deployment is managed=true and deployer API is NOT used. In this case, the classes have a different class loader > In the test below, I tried to load different versions of Infinispan in two deployments and test backward compatibility. However, due to this class loading issue the Infinispan classes are of the latest version regardless of libraries bundled in the WAR. This is probably due to the fact that the Maven test module has the latest Infinispan libraries defined in while the older version is downloaded separately via Maven dependency plugin. > {code} > package com.jboss.datagrid.test.backwardcompatibility; > @RunWith(Arquillian.class) > public class SingleFileStoreBackwardCompatibilityIT { > private DefaultCacheManager dfc; > private String cacheName = "testCache"; > private static final String OLD_ISPN = "dep1_with_old_ispn"; > private static final String NEW_ISPN = "dep2_with_new_ispn"; > private static Map storedMap; > @ArquillianResource > Deployer deployer; > @Deployment(name = OLD_ISPN, testable = true, managed = true, order=1) > @TargetsContainer("container1") > public static WebArchive createDeploymentOld() { > WebArchive jar = DeploymentBuilder.createTestArchiveWithPreviousJDG("test1.war", "previous"); > System.out.println("ClassLoader: " + SingleFileStoreBackwardCompatibilityIT.class.getClassLoader()); > return jar; > } > @Deployment(name = NEW_ISPN, testable = true, managed = true, order=2) > @TargetsContainer("container2") > public static WebArchive createDeploymentNew() { > WebArchive jar = DeploymentBuilder.createTestArchive("test2.war", "current"); > return jar; > } > private DefaultCacheManager configureCacheManager(boolean clearCacheStore) throws Exception { > GlobalConfiguration glob = new GlobalConfigurationBuilder().nonClusteredDefault() > .globalJmxStatistics().allowDuplicateDomains(true). > build(); > ConfigurationBuilder c = new ConfigurationBuilder(); > c.clustering().cacheMode(CacheMode.LOCAL); > File tmpStore = new File("/tmp/cache/" + cacheName + ".dat"); > if (clearCacheStore && tmpStore.exists()) { > tmpStore.delete(); > } > c.persistence().passivation(false).addSingleFileStore().purgeOnStartup(false).location("/tmp/cache/"); > Configuration cnf = c.build(); > DefaultCacheManager manager = new DefaultCacheManager(glob); > manager.defineConfiguration(cacheName, cnf); > return manager; > } > @Test > @OperateOnDeployment(OLD_ISPN) > @InSequence(1) > public void testStoreWithOldJDG() throws Exception { > deployer.deploy(OLD_ISPN); > dfc = configureCacheManager(true); > dfc.start(); > Cache cache = dfc.getCache(cacheName); > System.out.println("Version: " + cache.getVersion()); > System.out.println("ClassLoader: " + cache.getClass().getClassLoader()); > storedMap = new HashMap(); > storedMap.put("k", "v"); > cache.put("mapKey", storedMap); > dfc.stop(); > deployer.undeploy(OLD_ISPN); > } > @Test > @OperateOnDeployment(NEW_ISPN) > @InSequence(2) > public void testReadWithNewJDG() throws Exception { > deployer.deploy(NEW_ISPN); > dfc = configureCacheManager(false); > dfc.start(); > Cache cache = dfc.getCache(cacheName); > System.out.println("ClassLoader: " + cache.getClass().getClassLoader()); > System.out.println("Version: " + cache.getVersion()); > assertEquals(storedMap, cache.get("mapKey")); > dfc.stop(); > deployer.undeploy(NEW_ISPN); > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 12:21:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 12:21:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1954) Support @Rule enrichement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1954. ------------------------------ > Support @Rule enrichement > ------------------------- > > Key: ARQ-1954 > URL: https://issues.jboss.org/browse/ARQ-1954 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.8.Final > Reporter: Karel Piwko > Fix For: 1.1.11.Final > > > Arquillian should by default enrich JUnit @Rule statements. > Similarly to https://github.com/aerogear/aerogear-testing-tools/blob/master/arquillian-rule/src/test/java/org/jboss/aerogear/arquillian/junit/RuleInjectionTest.java -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 12:21:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 12:21:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2009) ServletProtocol depend on Servlet 3.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-2009. ------------------------------ > ServletProtocol depend on Servlet 3.0 > ------------------------------------- > > Key: ARQ-2009 > URL: https://issues.jboss.org/browse/ARQ-2009 > Project: Arquillian > Issue Type: Bug > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.10.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 12:21:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 12:21:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1937) Class loading issue with injected deployer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1937. ------------------------------ > Class loading issue with injected deployer > ------------------------------------------- > > Key: ARQ-1937 > URL: https://issues.jboss.org/browse/ARQ-1937 > Project: Arquillian > Issue Type: Bug > Components: Deployable Containers SPI > Affects Versions: 1.1.1.Final > Reporter: Martin Gencur > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > > Steps to reproduce: > 1) inject a Deployer via @ArquillianResource > 2) declare a deployment as managed=false, use the deployer to deploy artifacts to a managed container > 3) run a test method that operates on the deployment > 4) check that classes inside the test method have the same classloader as the test class itself (see the code below where I call cache.getClass().getClassLoader()) > 5) this does not happen when the deployment is managed=true and deployer API is NOT used. In this case, the classes have a different class loader > In the test below, I tried to load different versions of Infinispan in two deployments and test backward compatibility. However, due to this class loading issue the Infinispan classes are of the latest version regardless of libraries bundled in the WAR. This is probably due to the fact that the Maven test module has the latest Infinispan libraries defined in while the older version is downloaded separately via Maven dependency plugin. > {code} > package com.jboss.datagrid.test.backwardcompatibility; > @RunWith(Arquillian.class) > public class SingleFileStoreBackwardCompatibilityIT { > private DefaultCacheManager dfc; > private String cacheName = "testCache"; > private static final String OLD_ISPN = "dep1_with_old_ispn"; > private static final String NEW_ISPN = "dep2_with_new_ispn"; > private static Map storedMap; > @ArquillianResource > Deployer deployer; > @Deployment(name = OLD_ISPN, testable = true, managed = true, order=1) > @TargetsContainer("container1") > public static WebArchive createDeploymentOld() { > WebArchive jar = DeploymentBuilder.createTestArchiveWithPreviousJDG("test1.war", "previous"); > System.out.println("ClassLoader: " + SingleFileStoreBackwardCompatibilityIT.class.getClassLoader()); > return jar; > } > @Deployment(name = NEW_ISPN, testable = true, managed = true, order=2) > @TargetsContainer("container2") > public static WebArchive createDeploymentNew() { > WebArchive jar = DeploymentBuilder.createTestArchive("test2.war", "current"); > return jar; > } > private DefaultCacheManager configureCacheManager(boolean clearCacheStore) throws Exception { > GlobalConfiguration glob = new GlobalConfigurationBuilder().nonClusteredDefault() > .globalJmxStatistics().allowDuplicateDomains(true). > build(); > ConfigurationBuilder c = new ConfigurationBuilder(); > c.clustering().cacheMode(CacheMode.LOCAL); > File tmpStore = new File("/tmp/cache/" + cacheName + ".dat"); > if (clearCacheStore && tmpStore.exists()) { > tmpStore.delete(); > } > c.persistence().passivation(false).addSingleFileStore().purgeOnStartup(false).location("/tmp/cache/"); > Configuration cnf = c.build(); > DefaultCacheManager manager = new DefaultCacheManager(glob); > manager.defineConfiguration(cacheName, cnf); > return manager; > } > @Test > @OperateOnDeployment(OLD_ISPN) > @InSequence(1) > public void testStoreWithOldJDG() throws Exception { > deployer.deploy(OLD_ISPN); > dfc = configureCacheManager(true); > dfc.start(); > Cache cache = dfc.getCache(cacheName); > System.out.println("Version: " + cache.getVersion()); > System.out.println("ClassLoader: " + cache.getClass().getClassLoader()); > storedMap = new HashMap(); > storedMap.put("k", "v"); > cache.put("mapKey", storedMap); > dfc.stop(); > deployer.undeploy(OLD_ISPN); > } > @Test > @OperateOnDeployment(NEW_ISPN) > @InSequence(2) > public void testReadWithNewJDG() throws Exception { > deployer.deploy(NEW_ISPN); > dfc = configureCacheManager(false); > dfc.start(); > Cache cache = dfc.getCache(cacheName); > System.out.println("ClassLoader: " + cache.getClass().getClassLoader()); > System.out.println("Version: " + cache.getVersion()); > assertEquals(storedMap, cache.get("mapKey")); > dfc.stop(); > deployer.undeploy(NEW_ISPN); > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 12:21:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 12:21:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2010) Report first Exception caught in TestRunner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-2010. ------------------------------ > Report first Exception caught in TestRunner > ------------------------------------------- > > Key: ARQ-2010 > URL: https://issues.jboss.org/browse/ARQ-2010 > Project: Arquillian > Issue Type: Enhancement > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.10.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > > In particular when testing with the Arquillian Persistence extension it can be very difficult to diagnose problems in a test: > Usually when seeding of the database fails some other After event listener fails as well, e.g. evaluation of @ShouldMatchDataSet. > Then Arquillian only reports the last error that the actual result differs from the expected one. > This makes fixing the test very hard. > This PR changes the JUnitTestRunner so that it keeps the first exception that passes by ExpectedExceptionHolder.testFailure() instead of the last one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 12:21:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 27 Jan 2016 12:21:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1996) Upgrade to ShrinkWrap 1.2.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1996. ------------------------------ > Upgrade to ShrinkWrap 1.2.3 > --------------------------- > > Key: ARQ-1996 > URL: https://issues.jboss.org/browse/ARQ-1996 > Project: Arquillian > Issue Type: Component Upgrade > Components: Base Implementation > Affects Versions: 1.1.10.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.11.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 28 07:31:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 28 Jan 2016 07:31:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1973) Creates client enrichment for ServletContext In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1973: ------------------------------- Fix Version/s: jetty_1.0.0.next > Creates client enrichment for ServletContext > -------------------------------------------- > > Key: ARQ-1973 > URL: https://issues.jboss.org/browse/ARQ-1973 > Project: Arquillian > Issue Type: Feature Request > Components: Jetty Containers > Affects Versions: jetty_1.0.0.CR2 > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: jetty_1.0.0.next > > > Adds {{ResourceProvider}} for {{ServletContext}} created in embedded Jetty for tests run in client mode. > {code:java} > @ArquillianResource > ServletContext servletContext; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 28 07:32:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 28 Jan 2016 07:32:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1973) Creates client enrichment for ServletContext In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1973: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Creates client enrichment for ServletContext > -------------------------------------------- > > Key: ARQ-1973 > URL: https://issues.jboss.org/browse/ARQ-1973 > Project: Arquillian > Issue Type: Feature Request > Components: Jetty Containers > Affects Versions: jetty_1.0.0.CR2 > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: jetty_1.0.0.next > > > Adds {{ResourceProvider}} for {{ServletContext}} created in embedded Jetty for tests run in client mode. > {code:java} > @ArquillianResource > ServletContext servletContext; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 28 07:36:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 28 Jan 2016 07:36:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1973) Creates client enrichment for ServletContext In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1973: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Creates client enrichment for ServletContext > -------------------------------------------- > > Key: ARQ-1973 > URL: https://issues.jboss.org/browse/ARQ-1973 > Project: Arquillian > Issue Type: Feature Request > Components: Jetty Containers > Affects Versions: jetty_1.0.0.CR2 > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: jetty_1.0.0.next > > > Adds {{ResourceProvider}} for {{ServletContext}} created in embedded Jetty for tests run in client mode. > {code:java} > @ArquillianResource > ServletContext servletContext; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 28 07:39:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 28 Jan 2016 07:39:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1973) Creates client enrichment for ServletContext In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1973: ------------------------------- Fix Version/s: jetty_1.0.0.CR3 (was: jetty_1.0.0.next) > Creates client enrichment for ServletContext > -------------------------------------------- > > Key: ARQ-1973 > URL: https://issues.jboss.org/browse/ARQ-1973 > Project: Arquillian > Issue Type: Feature Request > Components: Jetty Containers > Affects Versions: jetty_1.0.0.CR2 > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: jetty_1.0.0.CR3 > > > Adds {{ResourceProvider}} for {{ServletContext}} created in embedded Jetty for tests run in client mode. > {code:java} > @ArquillianResource > ServletContext servletContext; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 28 07:39:01 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 28 Jan 2016 07:39:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1972) Add support for mimetypes, header buffer size and user realms in configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1972: ------------------------------- Fix Version/s: jetty_1.0.0.CR3 > Add support for mimetypes, header buffer size and user realms in configuration > ------------------------------------------------------------------------------ > > Key: ARQ-1972 > URL: https://issues.jboss.org/browse/ARQ-1972 > Project: Arquillian > Issue Type: Feature Request > Components: Jetty Containers > Affects Versions: jetty_1.0.0.CR2 > Reporter: Aslak Knutsen > Fix For: jetty_1.0.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 28 08:38:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 28 Jan 2016 08:38:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1972) Add support for mimetypes, header buffer size and user realms in configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1972. ------------------------------ > Add support for mimetypes, header buffer size and user realms in configuration > ------------------------------------------------------------------------------ > > Key: ARQ-1972 > URL: https://issues.jboss.org/browse/ARQ-1972 > Project: Arquillian > Issue Type: Feature Request > Components: Jetty Containers > Affects Versions: jetty_1.0.0.CR2 > Reporter: Aslak Knutsen > Fix For: jetty_1.0.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 28 08:38:00 2016 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 28 Jan 2016 08:38:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1973) Creates client enrichment for ServletContext In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1973. ------------------------------ > Creates client enrichment for ServletContext > -------------------------------------------- > > Key: ARQ-1973 > URL: https://issues.jboss.org/browse/ARQ-1973 > Project: Arquillian > Issue Type: Feature Request > Components: Jetty Containers > Affects Versions: jetty_1.0.0.CR2 > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: jetty_1.0.0.CR3 > > > Adds {{ResourceProvider}} for {{ServletContext}} created in embedded Jetty for tests run in client mode. > {code:java} > @ArquillianResource > ServletContext servletContext; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 28 21:41:00 2016 From: issues at jboss.org (Marc Richards (JIRA)) Date: Thu, 28 Jan 2016 21:41:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156200#comment-13156200 ] Marc Richards commented on ARQ-1944: ------------------------------------ I ran into this error using arquillian-tomcat-embedded with Tomcat 7.0.52 and 8.0.28. It appears that a change was made to the which classloader is used by default for Tomcat versions after 7.5.0: https://bz.apache.org/bugzilla/show_bug.cgi?id=55943 https://tomcat.apache.org/tomcat-7.0-doc/changelog.html#Tomcat 7.0.51 (violetagg) https://tomcat.apache.org/tomcat-8.0-doc/class-loader-howto.html#Class_Loader_Definitions I was able to successfully work around the issue by adding the following line to context.xml: > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.50 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in three different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 03:55:00 2016 From: issues at jboss.org (Chris Rankin (JIRA)) Date: Fri, 29 Jan 2016 03:55:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Rankin updated ARQ-1944: ------------------------------ Description: Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). The test fails with this error message: {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) {code} This error can be resolved in three different ways: - Rewrite the test using TestNG - Rewrite the test without using any Hamcrest matchers. - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] was: Testing a WAR in embedded Tomcat >= 7.0.50 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). The test fails with this error message: {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) {code} This error can be resolved in three different ways: - Rewrite the test using TestNG - Rewrite the test without using any Hamcrest matchers. - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in three different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 04:01:00 2016 From: issues at jboss.org (Chris Rankin (JIRA)) Date: Fri, 29 Jan 2016 04:01:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156295#comment-13156295 ] Chris Rankin commented on ARQ-1944: ----------------------------------- Confirm that Tomcat 7.0.50 is actually unaffected, although I have also needed to downgrade my example project to use arquillian-tomcat-embedded-7:1.0.0.CR5 for this version to pass. Adding {code:XML}{code} to the context.xml also works, although I wouldn't want to fundamentally alter how Tomcat behaves just to work around an Arquillian bug. > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in three different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 04:03:00 2016 From: issues at jboss.org (Chris Rankin (JIRA)) Date: Fri, 29 Jan 2016 04:03:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Rankin updated ARQ-1944: ------------------------------ Affects Version/s: 1.1.11.Final 1.1.10.Final 1.1.9.Final > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in three different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:58:00 2016 From: issues at jboss.org (Chris Rankin (JIRA)) Date: Fri, 29 Jan 2016 08:58:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156295#comment-13156295 ] Chris Rankin edited comment on ARQ-1944 at 1/29/16 8:57 AM: ------------------------------------------------------------ Confirmed that Tomcat 7.0.50 is actually unaffected, although I have also needed to downgrade my example project to use arquillian-tomcat-embedded-7:1.0.0.CR5 for this version to pass. Adding {code:XML}{code} to the context.xml also works, although I wouldn't want fundamentally to alter how Tomcat behaves just to work around a problem with using Arquillian! was (Author: chrisjr): Confirm that Tomcat 7.0.50 is actually unaffected, although I have also needed to downgrade my example project to use arquillian-tomcat-embedded-7:1.0.0.CR5 for this version to pass. Adding {code:XML}{code} to the context.xml also works, although I wouldn't want to fundamentally alter how Tomcat behaves just to work around an Arquillian bug. > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in three different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 11:37:00 2016 From: issues at jboss.org (Chris Rankin (JIRA)) Date: Fri, 29 Jan 2016 11:37:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156576#comment-13156576 ] Chris Rankin commented on ARQ-1944: ----------------------------------- In my _particular_ case, I am deploying a ROOT.war file into an embedded Tomcat and then testing its HTTP endpoints. This means that I don't really need the Arquillian JARs to be packaged into my WAR at all! I can therefore do this: {code}@Deployment(testable = false) public static WebArchive createDeployment() { return ShrinkWrap.creaste(WebArchive.class, "ROOT.war") ...; } {code} And then annotate all of my test cases as: {code}@RunWith(Arquillian.class) @RunAsClient public class MyTestCaseIT { ... } {code} The point here is that {{@Deployment(testable = false)}} effectively stops Arquillian from including the extra and unwanted Hamcrest artifact. > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in three different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 11:38:00 2016 From: issues at jboss.org (Chris Rankin (JIRA)) Date: Fri, 29 Jan 2016 11:38:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156576#comment-13156576 ] Chris Rankin edited comment on ARQ-1944 at 1/29/16 11:37 AM: ------------------------------------------------------------- In my _particular_ case, I am deploying a ROOT.war file into an embedded Tomcat and then testing its HTTP endpoints. This means that I don't really need the Arquillian JARs to be packaged into my WAR at all! I can therefore do this: {code}@Deployment(testable = false) public static WebArchive createDeployment() { return ShrinkWrap.create(WebArchive.class, "ROOT.war") ...; } {code} And then annotate all of my test cases as: {code}@RunWith(Arquillian.class) @RunAsClient public class MyTestCaseIT { ... } {code} The point here is that {{@Deployment(testable = false)}} effectively stops Arquillian from including the extra and unwanted Hamcrest artifact. was (Author: chrisjr): In my _particular_ case, I am deploying a ROOT.war file into an embedded Tomcat and then testing its HTTP endpoints. This means that I don't really need the Arquillian JARs to be packaged into my WAR at all! I can therefore do this: {code}@Deployment(testable = false) public static WebArchive createDeployment() { return ShrinkWrap.creaste(WebArchive.class, "ROOT.war") ...; } {code} And then annotate all of my test cases as: {code}@RunWith(Arquillian.class) @RunAsClient public class MyTestCaseIT { ... } {code} The point here is that {{@Deployment(testable = false)}} effectively stops Arquillian from including the extra and unwanted Hamcrest artifact. > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in three different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 11:43:00 2016 From: issues at jboss.org (Chris Rankin (JIRA)) Date: Fri, 29 Jan 2016 11:43:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Rankin updated ARQ-1944: ------------------------------ Description: Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). The test fails with this error message: {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) {code} This error can be resolved in four different ways: - Rewrite the test using TestNG - Rewrite the test without using any Hamcrest matchers. - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place. See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] was: Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). The test fails with this error message: {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) {code} This error can be resolved in three different ways: - Rewrite the test using TestNG - Rewrite the test without using any Hamcrest matchers. - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in four different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Jan 30 17:44:00 2016 From: issues at jboss.org (Marc Richards (JIRA)) Date: Sat, 30 Jan 2016 17:44:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156200#comment-13156200 ] Marc Richards edited comment on ARQ-1944 at 1/30/16 5:43 PM: ------------------------------------------------------------- I ran into this error using arquillian-tomcat-embedded with Tomcat 7.0.52 and 8.0.28. It appears that a change was made to the which classloader is used by default for Tomcat versions after 7.0.50: https://bz.apache.org/bugzilla/show_bug.cgi?id=55943 https://tomcat.apache.org/tomcat-7.0-doc/changelog.html#Tomcat 7.0.51 (violetagg) https://tomcat.apache.org/tomcat-8.0-doc/class-loader-howto.html#Class_Loader_Definitions I was able to successfully work around the issue by adding the following line to context.xml: was (Author: talawahdotnet): I ran into this error using arquillian-tomcat-embedded with Tomcat 7.0.52 and 8.0.28. It appears that a change was made to the which classloader is used by default for Tomcat versions after 7.5.0: https://bz.apache.org/bugzilla/show_bug.cgi?id=55943 https://tomcat.apache.org/tomcat-7.0-doc/changelog.html#Tomcat 7.0.51 (violetagg) https://tomcat.apache.org/tomcat-8.0-doc/class-loader-howto.html#Class_Loader_Definitions I was able to successfully work around the issue by adding the following line to context.xml: > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in four different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Jan 30 18:23:00 2016 From: issues at jboss.org (Marc Richards (JIRA)) Date: Sat, 30 Jan 2016 18:23:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156774#comment-13156774 ] Marc Richards commented on ARQ-1944: ------------------------------------ Just wanted to add a few clarifications from my own testing as well 1) Yea, the latest releases of arquillian-tomcat-embedded have a bug when used with tomcat versions lower than 7.0.52, which makes the issue even more tricky: https://issues.jboss.org/browse/ARQ-1965 2) My errors are not related to hamcrest at all, the loader constraint violations are thrown for my own classes e.g. {code:java} java.lang.LinkageError: loader constraint violation: when resolving method "myorg.model.PollingEvent.(Lorg/joda/time/DateTime;Lmyorg/rest/model/OrderStatus;Lorg/joda/time/DateTime;)V" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, myorg/db/PollingEventManager, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for the method's defining class, myorg/model/PollingEvent, have different Class objects for the type myorg/rest/model/OrderStatus used in the signature {code} or {code:java} java.lang.LinkageError: loader constraint violation: loader (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading for a different type with name "myorg/rest/model/Product" {code} 3) Using @RunAsClient does workaround the issue for me as well except for some tests, however some tests make use of features of the app server and cannot be run as client 3) > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in four different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Jan 30 18:23:00 2016 From: issues at jboss.org (Marc Richards (JIRA)) Date: Sat, 30 Jan 2016 18:23:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156774#comment-13156774 ] Marc Richards edited comment on ARQ-1944 at 1/30/16 6:22 PM: ------------------------------------------------------------- Just wanted to add a few clarifications from my own testing as well 1) Yea, the latest releases of arquillian-tomcat-embedded have a bug when used with tomcat versions lower than 7.0.52, which makes the issue even more tricky: https://issues.jboss.org/browse/ARQ-1965 2) My errors are not related to hamcrest at all, the loader constraint violations are thrown for my own classes e.g. {code:java} java.lang.LinkageError: loader constraint violation: when resolving method "myorg.model.PollingEvent.(Lorg/joda/time/DateTime;Lmyorg/rest/model/OrderStatus;Lorg/joda/time/DateTime;)V" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, myorg/db/PollingEventManager, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for the method's defining class, myorg/model/PollingEvent, have different Class objects for the type myorg/rest/model/OrderStatus used in the signature {code} or {code:java} java.lang.LinkageError: loader constraint violation: loader (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading for a different type with name "myorg/rest/model/Product" {code} 3) Using @RunAsClient does workaround the issue for me as well except for some tests, however some tests make use of features of the app server and cannot be run as client was (Author: talawahdotnet): Just wanted to add a few clarifications from my own testing as well 1) Yea, the latest releases of arquillian-tomcat-embedded have a bug when used with tomcat versions lower than 7.0.52, which makes the issue even more tricky: https://issues.jboss.org/browse/ARQ-1965 2) My errors are not related to hamcrest at all, the loader constraint violations are thrown for my own classes e.g. {code:java} java.lang.LinkageError: loader constraint violation: when resolving method "myorg.model.PollingEvent.(Lorg/joda/time/DateTime;Lmyorg/rest/model/OrderStatus;Lorg/joda/time/DateTime;)V" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, myorg/db/PollingEventManager, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for the method's defining class, myorg/model/PollingEvent, have different Class objects for the type myorg/rest/model/OrderStatus used in the signature {code} or {code:java} java.lang.LinkageError: loader constraint violation: loader (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading for a different type with name "myorg/rest/model/Product" {code} 3) Using @RunAsClient does workaround the issue for me as well except for some tests, however some tests make use of features of the app server and cannot be run as client 3) > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in four different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Jan 31 09:03:00 2016 From: issues at jboss.org (Chris Rankin (JIRA)) Date: Sun, 31 Jan 2016 09:03:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156784#comment-13156784 ] Chris Rankin commented on ARQ-1944: ----------------------------------- I find your linkage error to be very strange. The reason that there's a problem with the Hamcrest matchers is that an extra copy of {{org.hamcrest.*}} is bundled inside the {{arquillian-junit.jar}} object that Arquillian includes to make a deployment "testable". Removing the duplicate Hamcrest objects (by whatever means) therefore resolves the problem. Assuming that your problem is fundamentally the same as mine, this would imply that you also have duplicated objects somewhere ({{org.joda.time.*}} perhaps?). I suggest examining the artifacts that Arquillian deploys by adding these lines to your {{arquillian.xml}} file: {code:XML} target/deployments {code} > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in four different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Jan 31 15:03:00 2016 From: issues at jboss.org (Chris Rankin (JIRA)) Date: Sun, 31 Jan 2016 15:03:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with arquillian-junit.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156784#comment-13156784 ] Chris Rankin edited comment on ARQ-1944 at 1/31/16 3:02 PM: ------------------------------------------------------------ I find your linkage error to be very strange. The reason that there's a problem with the Hamcrest matchers is that an extra copy of {{org.hamcrest.*}} is bundled inside the {{arquillian-junit.jar}} object that Arquillian includes to make a deployment "testable". Removing the duplicate Hamcrest objects (by whatever means) therefore resolves the problem. Assuming that your problem is fundamentally the same as mine, this would imply that you also have duplicated objects somewhere -({{org.joda.time.*}} perhaps?)-. I suggest examining the artifacts that Arquillian deploys by adding these lines to your {{arquillian.xml}} file: {code:XML} target/deployments {code} Hmm, a closer look at the error suggests that {{myorg/rest/model/OrderStatus}} could be your problem: possibly the same class packaged into multiple jars, or maybe even two different implementations with the same class name? was (Author: chrisjr): I find your linkage error to be very strange. The reason that there's a problem with the Hamcrest matchers is that an extra copy of {{org.hamcrest.*}} is bundled inside the {{arquillian-junit.jar}} object that Arquillian includes to make a deployment "testable". Removing the duplicate Hamcrest objects (by whatever means) therefore resolves the problem. Assuming that your problem is fundamentally the same as mine, this would imply that you also have duplicated objects somewhere ({{org.joda.time.*}} perhaps?). I suggest examining the artifacts that Arquillian deploys by adding these lines to your {{arquillian.xml}} file: {code:XML} target/deployments {code} > Linkage error with arquillian-junit.jar > --------------------------------------- > > Key: ARQ-1944 > URL: https://issues.jboss.org/browse/ARQ-1944 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final > Environment: JDK7, Windows 7 x64, Linux x64 > Reporter: Chris Rankin > Attachments: arquillian-hamcrest-test.tar.xz > > > Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine). > The test fails with this error message: > {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT > testTrouble(org.testing.web.TroubleIT) Time elapsed: 0.774 sec <<< ERROR! > java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature > at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35) > {code} > This error can be resolved in four different ways: > - Rewrite the test using TestNG > - Rewrite the test without using any Hamcrest matchers. > - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}. > - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place. > See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78] -- This message was sent by Atlassian JIRA (v6.4.11#64026)