From issues at jboss.org Sun Jun 1 01:49:15 2014 From: issues at jboss.org (Chris Jones (JIRA)) Date: Sun, 1 Jun 2014 01:49:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: Chris Jones created ARQGRA-446: ---------------------------------- Summary: Add support for Groovy page objects Key: ARQGRA-446 URL: https://issues.jboss.org/browse/ARQGRA-446 Project: Arquillian Graphene Issue Type: Enhancement Components: configuration, core Affects Versions: 2.0.2.Final Reporter: Chris Jones Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. {code:title=GoogleGroovy.groovy|borderStyle=solid} package test import org.jboss.arquillian.graphene.page.Location import org.openqa.selenium.WebElement import org.openqa.selenium.support.FindBy @Location("https://www.google.com/") public class GoogleGroovy { @FindBy WebElement q def search(String query){ q.sendKeys(query) sleep(5000) } } {code} {code:title=GoogleJava.java|borderStyle=solid} package test; import org.jboss.arquillian.graphene.page.Location; import org.openqa.selenium.WebElement; import org.openqa.selenium.support.FindBy; @Location("https://www.google.com/") public class GoogleJava { @FindBy WebElement q; public void search(String query) throws Exception { q.sendKeys(query); Thread.sleep(5000); } } {code} {code:title=GoogleTestCase.groovy|borderStyle=solid} package test import org.jboss.arquillian.drone.api.annotation.Drone import org.jboss.arquillian.graphene.Graphene import org.jboss.arquillian.junit.Arquillian import org.junit.Test import org.junit.runner.RunWith import org.openqa.selenium.firefox.FirefoxDriver @RunWith(Arquillian.class) class GoogleTestCase { @Drone FirefoxDriver driver @Test def void testUsingJava(){ def googleJava = Graphene.goTo(GoogleJava) googleJava.search("hello world") } @Test def void testUsingGroovy(){ def googleGroovy = Graphene.goTo(GoogleGroovy) googleGroovy.search("jello world") } } {code} {code:title=Stacktrace|borderStyle=solid} Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. java.lang.StackOverflowError at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) ..... {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun Jun 1 01:51:15 2014 From: issues at jboss.org (Chris Jones (JIRA)) Date: Sun, 1 Jun 2014 01:51:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Jones updated ARQGRA-446: ------------------------------- Attachment: graphene-groovy-test.zip Attaching a test case > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Attachments: graphene-groovy-test.zip > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 02:33:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 02:33:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972236#comment-12972236 ] Luk?? Fry? commented on ARQGRA-446: ----------------------------------- Hey Chris, nice catch. Any suggestion how to avoid this issue? Is that just metaclass property that needs to be avoided in Groovy ecosystem or are we facing bigger issue? > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Attachments: graphene-groovy-test.zip > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:21:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:21:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-447) HtmlUnit does not support XHR2 - Switch functional tests to run on PhantomJS In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-447: --------------------------------- Summary: HtmlUnit does not support XHR2 - Switch functional tests to run on PhantomJS Key: ARQGRA-447 URL: https://issues.jboss.org/browse/ARQGRA-447 Project: Arquillian Graphene Issue Type: Task Affects Versions: 2.0.3.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 2.0.3.Final HtmlUnit does not support XHR2 yet: http://sourceforge.net/p/htmlunit/feature-requests/196/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:23:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:23:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-432) guardAjax does not work with XHR2 requests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-432: ------------------------------ Fix Version/s: 2.0.3.Final (was: 2.0-Tracking) > guardAjax does not work with XHR2 requests > ------------------------------------------ > > Key: ARQGRA-432 > URL: https://issues.jboss.org/browse/ARQGRA-432 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Priority: Critical > Fix For: 2.0.3.Final > > > {{guardAjax}} does not work correctly with XHR2 requests. The request is guarded correctly, but the callback once it is completed is not called. > The problem seems to be with {{onload}} (since XHR2) vs. {{onreadystatechange}} (since XHR1) callbacks. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:25:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:25:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-441: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/107 > xhrInterception breaks applications using jQuery 2.x > ---------------------------------------------------- > > Key: ARQGRA-441 > URL: https://issues.jboss.org/browse/ARQGRA-441 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final, 2.0.2.Final > Environment: Firefox 29, Chrome 34 > Reporter: Oliver Ki?? > Assignee: Oliver Ki?? > Priority: Critical > Fix For: 2.0.3.Final > > > After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. > After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). > When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. > I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:25:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:25:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-432) guardAjax does not work with XHR2 requests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-432: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/108 > guardAjax does not work with XHR2 requests > ------------------------------------------ > > Key: ARQGRA-432 > URL: https://issues.jboss.org/browse/ARQGRA-432 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Priority: Critical > Fix For: 2.0.3.Final > > > {{guardAjax}} does not work correctly with XHR2 requests. The request is guarded correctly, but the callback once it is completed is not called. > The problem seems to be with {{onload}} (since XHR2) vs. {{onreadystatechange}} (since XHR1) callbacks. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:27:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:27:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-448) Reuse PhantomJS instance during whole test suite In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-448: --------------------------------- Summary: Reuse PhantomJS instance during whole test suite Key: ARQGRA-448 URL: https://issues.jboss.org/browse/ARQGRA-448 Project: Arquillian Graphene Issue Type: Task Affects Versions: 2.0.3.Final Reporter: Luk?? Fry? Fix For: 2.0-Tracking -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:27:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:27:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-448) Reuse PhantomJS instance during whole test suite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-448: ------------------------------ Description: Tests are pretty slow on PhantomJS, I think that's because they need to start a new instance for every test case. > Reuse PhantomJS instance during whole test suite > ------------------------------------------------ > > Key: ARQGRA-448 > URL: https://issues.jboss.org/browse/ARQGRA-448 > Project: Arquillian Graphene > Issue Type: Task > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Fix For: 2.0-Tracking > > > Tests are pretty slow on PhantomJS, I think that's because they need to start a new instance for every test case. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:41:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:41:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-443) Upgrade to Core 1.1.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-443: ------------------------------ Fix Version/s: 2.0.3.Final > Upgrade to Core 1.1.4 > --------------------- > > Key: ARQGRA-443 > URL: https://issues.jboss.org/browse/ARQGRA-443 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:41:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:41:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-443) Upgrade to Core 1.1.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-443: ------------------------------ Summary: Upgrade to Core 1.1.4 (was: Upgrade to Core 1.1.4, Drone 1.3.1) > Upgrade to Core 1.1.4 > --------------------- > > Key: ARQGRA-443 > URL: https://issues.jboss.org/browse/ARQGRA-443 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Reporter: Luk?? Fry? > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:45:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:45:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-432) guardAjax does not work with XHR2 requests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-432: ------------------------------ Status: Resolved (was: Pull Request Sent) Assignee: Juraj H?ska Resolution: Done > guardAjax does not work with XHR2 requests > ------------------------------------------ > > Key: ARQGRA-432 > URL: https://issues.jboss.org/browse/ARQGRA-432 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Critical > Fix For: 2.0.3.Final > > > {{guardAjax}} does not work correctly with XHR2 requests. The request is guarded correctly, but the callback once it is completed is not called. > The problem seems to be with {{onload}} (since XHR2) vs. {{onreadystatechange}} (since XHR1) callbacks. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:45:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:45:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-441: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > xhrInterception breaks applications using jQuery 2.x > ---------------------------------------------------- > > Key: ARQGRA-441 > URL: https://issues.jboss.org/browse/ARQGRA-441 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final, 2.0.2.Final > Environment: Firefox 29, Chrome 34 > Reporter: Oliver Ki?? > Assignee: Oliver Ki?? > Priority: Critical > Fix For: 2.0.3.Final > > > After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. > After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). > When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. > I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:45:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:45:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-447) HtmlUnit does not support XHR2 - Switch functional tests to run on PhantomJS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQGRA-447. ------------------------------- Resolution: Done > HtmlUnit does not support XHR2 - Switch functional tests to run on PhantomJS > ---------------------------------------------------------------------------- > > Key: ARQGRA-447 > URL: https://issues.jboss.org/browse/ARQGRA-447 > Project: Arquillian Graphene > Issue Type: Task > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 2.0.3.Final > > > HtmlUnit does not support XHR2 yet: > http://sourceforge.net/p/htmlunit/feature-requests/196/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:45:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:45:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-443) Upgrade to Core 1.1.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQGRA-443. ------------------------------- Resolution: Done > Upgrade to Core 1.1.4 > --------------------- > > Key: ARQGRA-443 > URL: https://issues.jboss.org/browse/ARQGRA-443 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:45:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:45:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-443) Upgrade to Core 1.1.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned ARQGRA-443: --------------------------------- Assignee: Luk?? Fry? > Upgrade to Core 1.1.4 > --------------------- > > Key: ARQGRA-443 > URL: https://issues.jboss.org/browse/ARQGRA-443 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 2.0.3.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:49:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:49:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-433: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Assignee: Juraj H?ska > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 10:13:15 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 2 Jun 2014 10:13:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-445: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/109 > Wrong classes are injected to PageObject injection points in abstract test basis > -------------------------------------------------------------------------------- > > Key: ARQGRA-445 > URL: https://issues.jboss.org/browse/ARQGRA-445 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > > These tests fails because wrong instances are injected into abstract test basis: > {code} > Results : > Tests in error: > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 01:25:15 2014 From: issues at jboss.org (Chris Jones (JIRA)) Date: Tue, 3 Jun 2014 01:25:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972665#comment-12972665 ] Chris Jones commented on ARQGRA-446: ------------------------------------ I think that should do it. [This answer on SO|http://stackoverflow.com/a/18399011] suggests filtering metaclass and a few others. [Spring|https://github.com/spring-projects/spring-framework/tree/master/spring-context] also makes use of cglib and it works fine with groovy, though I couldn't find any mention of "metaclass" in it's source. Also see how [Jackson|http://jira.codehaus.org/browse/JACKSON-103] takes care of groovy's metaclass property. > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Attachments: graphene-groovy-test.zip > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 06:38:15 2014 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Tue, 3 Jun 2014 06:38:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1793) Release new version of arquillian-weld-ee-embedded with cdi-api 1.2 In-Reply-To: References: Message-ID: Tomas Remes created ARQ-1793: -------------------------------- Summary: Release new version of arquillian-weld-ee-embedded with cdi-api 1.2 Key: ARQ-1793 URL: https://issues.jboss.org/browse/ARQ-1793 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployable Containers SPI Affects Versions: weld_1.0.0.CR8 Reporter: Tomas Remes -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 06:42:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 3 Jun 2014 06:42:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-445: ------------------------------ Status: Resolved (was: Pull Request Sent) Assignee: Juraj H?ska Resolution: Done > Wrong classes are injected to PageObject injection points in abstract test basis > -------------------------------------------------------------------------------- > > Key: ARQGRA-445 > URL: https://issues.jboss.org/browse/ARQGRA-445 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 2.0.3.Final > > > These tests fails because wrong instances are injected into abstract test basis: > {code} > Results : > Tests in error: > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 08:14:16 2014 From: issues at jboss.org (Juan Casta (JIRA)) Date: Tue, 3 Jun 2014 08:14:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1309) Persistence extension does not work with Jacoco extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972799#comment-12972799 ] Juan Casta commented on ARQ-1309: --------------------------------- Hello. Still same error with jacoco extension 1.0.0.Alpha6 Arquillian 1.1.3.Final Arquillian Persistence 1.0.0.Alpha7 Added files to the issue Also explained here: https://community.jboss.org/message/876565#876565 > Persistence extension does not work with Jacoco extension > --------------------------------------------------------- > > Key: ARQ-1309 > URL: https://issues.jboss.org/browse/ARQ-1309 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: 1.0.0.Alpha5 > Reporter: Peter Schonhofen > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > When the Jacoco and persistence extension is used together in a project, a "PersistenceExtensionInitializationException: Unable to create persistence configuration" is thrown. > The cause of the exception is that in the ConfigurationImporter class the createConfiguration method receives a fieldsWithValues map with a "$jacocoData" item in it. Because the method cannot process this item, it fails. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:14:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:14:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973109#comment-12973109 ] Luk?? Fry? commented on ARQGRA-446: ----------------------------------- Chris, any chance you could try to implement a way around in the graphene code? I can give you hand with where to find things in the code base if necessary. > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Attachments: graphene-groovy-test.zip > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:16:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:16:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) Prevent FieldAccessValidatorEnricher from reporting issues with public fields in test class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-433: ------------------------------ Summary: Prevent FieldAccessValidatorEnricher from reporting issues with public fields in test class (was: FieldAccessValidatorEnricher checks access to fields uniformly) > Prevent FieldAccessValidatorEnricher from reporting issues with public fields in test class > ------------------------------------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Assignee: Juraj H?ska > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:18:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:18:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Make SeleniumResourceEnricher compatible with selenium 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-442: ------------------------------ Summary: Make SeleniumResourceEnricher compatible with selenium 2.42.0 (was: Graphene is not compatible with selenium 2.42.0) Issue Type: Enhancement (was: Feature Request) > Make SeleniumResourceEnricher compatible with selenium 2.42.0 > ------------------------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Enhancement > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Assignee: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:18:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:18:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Make SeleniumResourceProvider compatible with selenium 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-442: ------------------------------ Summary: Make SeleniumResourceProvider compatible with selenium 2.42.0 (was: Make SeleniumResourceEnricher compatible with selenium 2.42.0) > Make SeleniumResourceProvider compatible with selenium 2.42.0 > ------------------------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Enhancement > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Assignee: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:18:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:18:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-447) Switch functional tests to run on PhantomJS (HtmlUnit does not support XHR2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-447: ------------------------------ Summary: Switch functional tests to run on PhantomJS (HtmlUnit does not support XHR2) (was: HtmlUnit does not support XHR2 - Switch functional tests to run on PhantomJS) > Switch functional tests to run on PhantomJS (HtmlUnit does not support XHR2) > ---------------------------------------------------------------------------- > > Key: ARQGRA-447 > URL: https://issues.jboss.org/browse/ARQGRA-447 > Project: Arquillian Graphene > Issue Type: Task > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 2.0.3.Final > > > HtmlUnit does not support XHR2 yet: > http://sourceforge.net/p/htmlunit/feature-requests/196/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:18:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:18:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-447) Switch functional tests to run on PhantomJS by default (HtmlUnit does not support XHR2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-447: ------------------------------ Summary: Switch functional tests to run on PhantomJS by default (HtmlUnit does not support XHR2) (was: Switch functional tests to run on PhantomJS (HtmlUnit does not support XHR2)) > Switch functional tests to run on PhantomJS by default (HtmlUnit does not support XHR2) > --------------------------------------------------------------------------------------- > > Key: ARQGRA-447 > URL: https://issues.jboss.org/browse/ARQGRA-447 > Project: Arquillian Graphene > Issue Type: Task > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 2.0.3.Final > > > HtmlUnit does not support XHR2 yet: > http://sourceforge.net/p/htmlunit/feature-requests/196/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:20:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:20:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Make SeleniumResourceProvider compatible with Selenium API 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-442: ------------------------------ Summary: Make SeleniumResourceProvider compatible with Selenium API 2.42.0 (was: Make SeleniumResourceProvider compatible with selenium 2.42.0) > Make SeleniumResourceProvider compatible with Selenium API 2.42.0 > ----------------------------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Enhancement > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Assignee: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:20:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:20:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? closed ARQGRA-441. ----------------------------- > xhrInterception breaks applications using jQuery 2.x > ---------------------------------------------------- > > Key: ARQGRA-441 > URL: https://issues.jboss.org/browse/ARQGRA-441 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final, 2.0.2.Final > Environment: Firefox 29, Chrome 34 > Reporter: Oliver Ki?? > Assignee: Oliver Ki?? > Priority: Critical > Fix For: 2.0.3.Final > > > After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. > After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). > When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. > I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:20:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:20:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-447) Switch functional tests to run on PhantomJS by default (HtmlUnit does not support XHR2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? closed ARQGRA-447. ----------------------------- > Switch functional tests to run on PhantomJS by default (HtmlUnit does not support XHR2) > --------------------------------------------------------------------------------------- > > Key: ARQGRA-447 > URL: https://issues.jboss.org/browse/ARQGRA-447 > Project: Arquillian Graphene > Issue Type: Task > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 2.0.3.Final > > > HtmlUnit does not support XHR2 yet: > http://sourceforge.net/p/htmlunit/feature-requests/196/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:20:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:20:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-432) guardAjax does not work with XHR2 requests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? closed ARQGRA-432. ----------------------------- > guardAjax does not work with XHR2 requests > ------------------------------------------ > > Key: ARQGRA-432 > URL: https://issues.jboss.org/browse/ARQGRA-432 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Critical > Fix For: 2.0.3.Final > > > {{guardAjax}} does not work correctly with XHR2 requests. The request is guarded correctly, but the callback once it is completed is not called. > The problem seems to be with {{onload}} (since XHR2) vs. {{onreadystatechange}} (since XHR1) callbacks. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:20:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:20:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) Prevent FieldAccessValidatorEnricher from reporting issues with public fields in test class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? closed ARQGRA-433. ----------------------------- > Prevent FieldAccessValidatorEnricher from reporting issues with public fields in test class > ------------------------------------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Assignee: Juraj H?ska > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:20:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:20:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Make SeleniumResourceProvider compatible with Selenium API 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? closed ARQGRA-442. ----------------------------- > Make SeleniumResourceProvider compatible with Selenium API 2.42.0 > ----------------------------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Enhancement > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Assignee: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:20:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:20:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-444) Functional tests fail to run due to surefire plugin failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? closed ARQGRA-444. ----------------------------- > Functional tests fail to run due to surefire plugin failure > ----------------------------------------------------------- > > Key: ARQGRA-444 > URL: https://issues.jboss.org/browse/ARQGRA-444 > Project: Arquillian Graphene > Issue Type: Bug > Environment: $ mvn -v > Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) > Maven home: /home/lfryc/Apps/apache-maven-3.0.4 > Java version: 1.7.0_51, vendor: Oracle Corporation > Java home: /usr/java/jdk1.7.0_51/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.14.4-200.fc20.x86_64", arch: "amd64", family: "unix" > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 2.0.3.Final > > > {code} > [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ graphene-webdriver-ftest --- > [INFO] Surefire report directory: /mnt/workspace/workspaces/arquillian/arquillian-graphene/ftest/target/surefire-reports > [INFO] Using configured provider org.apache.maven.surefire.junitcore.JUnitCoreProvider > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false > Running org.jboss.arquillian.graphene.ftest.intercept.TestInterceptorRegistration > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec > Running org.jboss.arquillian.graphene.ftest.element.TestGrapheneElementAsPageFragmentRoot > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec > Running org.jboss.arquillian.graphene.ftest.enricher.hierarchy.SomeAbstractTest > Exception in thread "ThreadedStreamConsumer" java.lang.NoSuchMethodError: org.apache.maven.surefire.report.StackTraceWriter.getThrowable()Ljava/lang/Throwable; > at org.apache.maven.surefire.report.XMLReporter.writeTestProblems(XMLReporter.java:238) > at org.apache.maven.surefire.report.XMLReporter.testError(XMLReporter.java:208) > at org.apache.maven.surefire.report.MulticastingReporter.testError(MulticastingReporter.java:73) > at org.apache.maven.surefire.report.TestSetRunListener.testError(TestSetRunListener.java:139) > at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:112) > at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67) > at java.lang.Thread.run(Thread.java:744) > Results : > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:20:18 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:20:18 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-443) Upgrade to Core 1.1.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? closed ARQGRA-443. ----------------------------- > Upgrade to Core 1.1.4 > --------------------- > > Key: ARQGRA-443 > URL: https://issues.jboss.org/browse/ARQGRA-443 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 2.0.3.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 03:20:18 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Jun 2014 03:20:18 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? closed ARQGRA-445. ----------------------------- > Wrong classes are injected to PageObject injection points in abstract test basis > -------------------------------------------------------------------------------- > > Key: ARQGRA-445 > URL: https://issues.jboss.org/browse/ARQGRA-445 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 2.0.3.Final > > > These tests fails because wrong instances are injected into abstract test basis: > {code} > Results : > Tests in error: > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 05:38:15 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 6 Jun 2014 05:38:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQGRA-449: ---------------------------------------- Summary: Graphene can not switch between contexts Key: ARQGRA-449 URL: https://issues.jboss.org/browse/ARQGRA-449 Project: Arquillian Graphene Issue Type: Bug Components: core Affects Versions: 2.0.3.Final Reporter: Stefan Miklosovic This code: {code} @Test public void nativeViewTest() { driver.switchTo().window("NATIVE_APP"); } {code} That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. It produces this exception: java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) at com.sun.proxy.$Proxy27.window(Unknown Source) at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 05:38:16 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 6 Jun 2014 05:38:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974025#comment-12974025 ] Stefan Miklosovic commented on ARQGRA-449: ------------------------------------------ All was good with 2.0.2.Final > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 08:36:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 6 Jun 2014 08:36:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974109#comment-12974109 ] Luk?? Fry? commented on ARQGRA-449: ----------------------------------- Is it possible that the cause is upgrade of Selenium? > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 10:10:16 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 6 Jun 2014 10:10:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1794) Update dependecies for QUnit In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1794: -------------------------------------- Summary: Update dependecies for QUnit Key: ARQ-1794 URL: https://issues.jboss.org/browse/ARQ-1794 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - QUnit Affects Versions: qunit_1.0.0.Alpha3 Reporter: Stefan Miklosovic Assignee: Tolis Emmanouilidis Update jboss-parent to 14 selenium to 2.42.0 graphene to 2.0.3.Final arquillian-core to 1.1.4.Final -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 10:10:16 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 6 Jun 2014 10:10:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1794) Update dependecies for QUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1794: -------------------------------------- Assignee: Stefan Miklosovic (was: Tolis Emmanouilidis) > Update dependecies for QUnit > ---------------------------- > > Key: ARQ-1794 > URL: https://issues.jboss.org/browse/ARQ-1794 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - QUnit > Affects Versions: qunit_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > Update > jboss-parent to 14 > selenium to 2.42.0 > graphene to 2.0.3.Final > arquillian-core to 1.1.4.Final -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 10:22:17 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 6 Jun 2014 10:22:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974185#comment-12974185 ] Stefan Miklosovic commented on ARQGRA-449: ------------------------------------------ Dont know yet, my personal tip is that this error was introduced by changes in this commit (1), maybe [~sjamboro] could elaborate on this possibility? (1) https://github.com/arquillian/arquillian-graphene/commit/d75bd3a6cb29745ab71558a03634af5cc85610bc > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 10:50:16 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 6 Jun 2014 10:50:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1795) Update ghostdriver and phantom driver for Drone In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1795: -------------------------------------- Summary: Update ghostdriver and phantom driver for Drone Key: ARQ-1795 URL: https://issues.jboss.org/browse/ARQ-1795 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.3.0.Final Reporter: Stefan Miklosovic Update ghostdriver to 1.2.0 and phantom driver to 1.1.3.Final -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 10:50:16 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 6 Jun 2014 10:50:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1795) Update ghostdriver and phantom driver for Drone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1795: -------------------------------------- Assignee: Stefan Miklosovic > Update ghostdriver and phantom driver for Drone > ----------------------------------------------- > > Key: ARQ-1795 > URL: https://issues.jboss.org/browse/ARQ-1795 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > Update ghostdriver to 1.2.0 and phantom driver to 1.1.3.Final -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 10:52:15 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 6 Jun 2014 10:52:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1795) Update ghostdriver and phantom driver for Drone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1795: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/44 > Update ghostdriver and phantom driver for Drone > ----------------------------------------------- > > Key: ARQ-1795 > URL: https://issues.jboss.org/browse/ARQ-1795 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > Update ghostdriver to 1.2.0 and phantom driver to 1.1.3.Final -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 11:06:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 6 Jun 2014 11:06:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974202#comment-12974202 ] Luk?? Fry? commented on ARQGRA-449: ----------------------------------- I don't think it is related. According to the stack trace, it is caused by two incompatible APIs - ProxyGenerator tries to create a proxy for given interfaces and detects that there are two which contains {{#getContext()}} method, but returns different type. Stefan, could you please debug what interfaces we try to proxy that has conflicting signature? > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 11:06:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 6 Jun 2014 11:06:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974202#comment-12974202 ] Luk?? Fry? edited comment on ARQGRA-449 at 6/6/14 11:06 AM: ------------------------------------------------------------ I don't think it is related. According to the stack trace, it is caused by two incompatible APIs - ProxyGenerator tries to create a proxy for given interfaces and detects that there are two which contains {{#getContext()}} method, but returns different type. Stefan, could you please debug what interfaces we try to proxy that has conflicting signature? {code} interface I1 { String getContext(); } interface I2 { GrapheneContext getContext(); } {code} was (Author: lfryc): I don't think it is related. According to the stack trace, it is caused by two incompatible APIs - ProxyGenerator tries to create a proxy for given interfaces and detects that there are two which contains {{#getContext()}} method, but returns different type. Stefan, could you please debug what interfaces we try to proxy that has conflicting signature? > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat Jun 7 11:32:15 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 7 Jun 2014 11:32:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1767) Validate tool settings before it is executed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1767: -------------------------------------- Assignee: Stefan Miklosovic > Validate tool settings before it is executed > -------------------------------------------- > > Key: ARQ-1767 > URL: https://issues.jboss.org/browse/ARQ-1767 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > Implementator of Tool from Spacelift can use custom "setters" to prepare tool's environment or arguments before an execution. > In case this environment is not set properly or it misses, it fails too late or its handling is treated directly in process method which adds additional boilerplate code and it is not good approach in general. > Consider to add validate() method to Tool which would be called by Spacelift upon execute() call. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat Jun 7 12:34:15 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 7 Jun 2014 12:34:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1767) Validate tool settings before it is executed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1767: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-spacelift/pull/10 > Validate tool settings before it is executed > -------------------------------------------- > > Key: ARQ-1767 > URL: https://issues.jboss.org/browse/ARQ-1767 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > Implementator of Tool from Spacelift can use custom "setters" to prepare tool's environment or arguments before an execution. > In case this environment is not set properly or it misses, it fails too late or its handling is treated directly in process method which adds additional boilerplate code and it is not good approach in general. > Consider to add validate() method to Tool which would be called by Spacelift upon execute() call. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun Jun 8 15:38:15 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 8 Jun 2014 15:38:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1794) Update dependecies for QUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1794: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-qunit/pull/12 > Update dependecies for QUnit > ---------------------------- > > Key: ARQ-1794 > URL: https://issues.jboss.org/browse/ARQ-1794 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - QUnit > Affects Versions: qunit_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > Update > jboss-parent to 14 > selenium to 2.42.0 > graphene to 2.0.3.Final > arquillian-core to 1.1.4.Final -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 07:24:15 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 9 Jun 2014 07:24:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1749) Retrieve httpPort from MBean when not provided in configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul updated ARQ-1749: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: was_1.0.0.next Resolution: Done merged into master > Retrieve httpPort from MBean when not provided in configuration > --------------------------------------------------------------- > > Key: ARQ-1749 > URL: https://issues.jboss.org/browse/ARQ-1749 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > Fix For: was_1.0.0.next > > > The exposed MBean WebSphere/endpoint/channelfw/defaultHttpEndpoint contain Host and Port attributes which could be used if httpPort is not configured in arquillian.xml. > The Container require serverName to detect which VM is running, and as long as you have the VM you have the httpPort info. Defaulting to the 'defaultHttpEndpoint' should remove a few possible error configurations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 10:32:15 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 9 Jun 2014 10:32:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1756) wlp-managed arquillian support for wlp server assembly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974631#comment-12974631 ] Gerhard Poul commented on ARQ-1756: ----------------------------------- The maven tasks for liberty that are published on GitHub at https://github.com/WASdev/ci.maven also provide this functionality, so it might be relatively easy to add this. > wlp-managed arquillian support for wlp server assembly > ------------------------------------------------------ > > Key: ARQ-1756 > URL: https://issues.jboss.org/browse/ARQ-1756 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Reporter: D K > > Websphere liberty Maven plugin allows you to package a liberty server assembly and deploy it to repo Manager like Nexus: > https://github.com/WASdev/ci.maven#liberty-assembly > It would be good if the Liberty Arquillian container could be configured to download and use this liberty assembly. > https://github.com/arquillian/arquillian-container-was/tree/master/wlp-managed-8.5 > This mean each environment the tests run on would'nt need to be pre-installed with a Liberty server. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 10:34:17 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 9 Jun 2014 10:34:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1738) Liberty profile leave port 9080 hanging around after shutdown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974633#comment-12974633 ] Gerhard Poul commented on ARQ-1738: ----------------------------------- [~aslak] have you had time to look into this? Did Alasdair's suggestion resolve this? How do we want to proceed with this bug report? > Liberty profile leave port 9080 hanging around after shutdown > ------------------------------------------------------------- > > Key: ARQ-1738 > URL: https://issues.jboss.org/browse/ARQ-1738 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Environment: Fedora 20, Open JDK 7/8, Oracle JDK 7, WebSphere Application Server 8.5.5.1/wlp-1.0.4.cl50120131011-1639 > Reporter: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 12:45:16 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 9 Jun 2014 12:45:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1738) Liberty profile leave port 9080 hanging around after shutdown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1738. ------------------------------ Assignee: Aslak Knutsen Resolution: Out of Date Latest beta of version of Liberty fixes this issue. > Liberty profile leave port 9080 hanging around after shutdown > ------------------------------------------------------------- > > Key: ARQ-1738 > URL: https://issues.jboss.org/browse/ARQ-1738 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Environment: Fedora 20, Open JDK 7/8, Oracle JDK 7, WebSphere Application Server 8.5.5.1/wlp-1.0.4.cl50120131011-1639 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 07:45:16 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Tue, 10 Jun 2014 07:45:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1776) Create branch for OSGi containers compatible with OSGi 4.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1776: --------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/15, https://github.com/arquillian/arquillian-container-osgi/pull/25 (was: https://github.com/arquillian/arquillian-container-osgi/pull/15) > Create branch for OSGi containers compatible with OSGi 4.2 > ---------------------------------------------------------- > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/]. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 08:09:16 2014 From: issues at jboss.org (Sona Jamborova (JIRA)) Date: Tue, 10 Jun 2014 08:09:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974848#comment-12974848 ] Sona Jamborova commented on ARQGRA-449: --------------------------------------- Hi, I am not sure if code which I have changed is used by switchTo(). By the way if you use selenium 2.42.0, there are new versions of selenium (2.42.1 and 2.42.2). See https://code.google.com/p/selenium/source/browse/java/CHANGELOG > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 03:57:16 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 11 Jun 2014 03:57:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1748) Making html report with screenshooter on cp deletes target In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1748. ---------------------------------- > Making html report with screenshooter on cp deletes target > ---------------------------------------------------------- > > Key: ARQ-1748 > URL: https://issues.jboss.org/browse/ARQ-1748 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 03:59:16 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 11 Jun 2014 03:59:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1726) Reporter does not consider screenshots taken manually in test methods In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1726. ---------------------------------- > Reporter does not consider screenshots taken manually in test methods > --------------------------------------------------------------------- > > Key: ARQ-1726 > URL: https://issues.jboss.org/browse/ARQ-1726 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha3 > > > Beside screenshots taken automatically before / after test method according to configuration, user can take screenshots manually with screenshooter injection like this > {code} > @ArquillianResource Screenshooter screenshooter; > public void test() > { > screenshooter.takeScreenshot(); > } > {code} > It holds for Recoder injection point as well when user can record videos manually in test method like > {code} > @ArquillianResource Recoder recorder; > public void test() > { > recorder.start(); > // something is happening > recorder.stop(); > } > {code} > However, these screenshots and videos does not appear in final report file because when it is taken directly by injection interface, it does not fire any screenshot report event. Logic behind screenshooter and recorder knows this because it invokes screenshooter itself but concrete screenshooter implementation does not fire them. > There needs to be a way how to report these screenshots which were taken manually as well. > Taking of screenshots manually is the "last chance" for a user to take them exactly where he needs them to be taken and not showing them in report could be justified however due to user experience these should be taken into account as well definitely. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 03:59:16 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 11 Jun 2014 03:59:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1715) Merge release profile to default profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1715. ---------------------------------- > Merge release profile to default profile > ---------------------------------------- > > Key: ARQ-1715 > URL: https://issues.jboss.org/browse/ARQ-1715 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha3 > > > It does not make sense to have a separate profile -Prelease. > Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 03:59:17 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 11 Jun 2014 03:59:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1706) Add multilanguage to AsciiDocExporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1706. ---------------------------------- > Add multilanguage to AsciiDocExporter > ------------------------------------- > > Key: ARQ-1706 > URL: https://issues.jboss.org/browse/ARQ-1706 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Alex Soto > Priority: Minor > Fix For: recorder_1.0.0.Alpha3 > > > Add multi language to AsciiDocExporter. Currently AsciiDoc document is generated in English. Although Reporter extension allows users to set the language, AsciiDocExporter ignores it. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 03:59:17 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 11 Jun 2014 03:59:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1722) Name of Screenshooter method setting screenshot type is mangled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1722. ---------------------------------- > Name of Screenshooter method setting screenshot type is mangled > --------------------------------------------------------------- > > Key: ARQ-1722 > URL: https://issues.jboss.org/browse/ARQ-1722 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Trivial > Fix For: recorder_1.0.0.Alpha3 > > > Screenshooter interface has method "setScreensthotType" which is spelled wrongly. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 04:23:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 11 Jun 2014 04:23:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-450) takeBeforeTest takes screenshot only for first test when loading of page is done in @Before In-Reply-To: References: Message-ID: Juraj H?ska created ARQGRA-450: ---------------------------------- Summary: takeBeforeTest takes screenshot only for first test when loading of page is done in @Before Key: ARQGRA-450 URL: https://issues.jboss.org/browse/ARQGRA-450 Project: Arquillian Graphene Issue Type: Bug Components: screenshooter Affects Versions: 2.1.0.Alpha1 Reporter: Juraj H?ska As per ${SUBJECT}, {{takeBeforeTest}} option is broken, because when there are multiple tests, and the loading of the page is done on {{@Before}} method, then screenshot is taken only for first test. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 04:23:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 11 Jun 2014 04:23:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-450) takeBeforeTest takes screenshot only for first test when loading of page is done in @Before In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-450: ------------------------------- Description: {{takeBeforeTest}} option is broken, because when there are multiple tests, and the loading of the page is done on {{@Before}} method, then screenshot is taken only for first test. (was: As per ${SUBJECT}, {{takeBeforeTest}} option is broken, because when there are multiple tests, and the loading of the page is done on {{@Before}} method, then screenshot is taken only for first test.) > takeBeforeTest takes screenshot only for first test when loading of page is done in @Before > ------------------------------------------------------------------------------------------- > > Key: ARQGRA-450 > URL: https://issues.jboss.org/browse/ARQGRA-450 > Project: Arquillian Graphene > Issue Type: Bug > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > > {{takeBeforeTest}} option is broken, because when there are multiple tests, and the loading of the page is done on {{@Before}} method, then screenshot is taken only for first test. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 04:23:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 11 Jun 2014 04:23:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-450) takeBeforeTest takes screenshot only for first test when loading of page is done in @Before In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska reassigned ARQGRA-450: ---------------------------------- Assignee: Juraj H?ska > takeBeforeTest takes screenshot only for first test when loading of page is done in @Before > ------------------------------------------------------------------------------------------- > > Key: ARQGRA-450 > URL: https://issues.jboss.org/browse/ARQGRA-450 > Project: Arquillian Graphene > Issue Type: Bug > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > {{takeBeforeTest}} option is broken, because when there are multiple tests, and the loading of the page is done on {{@Before}} method, then screenshot is taken only for first test. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 04:33:15 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 11 Jun 2014 04:33:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1776) Create branch for OSGi containers compatible with OSGi 4.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated ARQ-1776: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Done > Create branch for OSGi containers compatible with OSGi 4.2 > ---------------------------------------------------------- > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/]. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 08:41:41 2014 From: issues at jboss.org (Daniel Latzer (JIRA)) Date: Wed, 11 Jun 2014 08:41:41 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1758) Test passes although it fails unexpectedly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975252#comment-12975252 ] Daniel Latzer commented on ARQ-1758: ------------------------------------ I just wanted to create a bug report for what i think is the same issue as this: A test that should clearly fail passes because of a failure to inject members. I managed to isolate the problem in a quickstart project: https://dl.dropboxusercontent.com/u/6070309/arq-pass-bug.tgz GreeterEJB doesn't implement GreeterRemote, thus it's obviously not possible to resolve the bean. If you fall back to Arquillian 1.1.3 an Exception is thrown, though with 1.1.4 the test just passes. > Test passes although it fails unexpectedly > ------------------------------------------ > > Key: ARQ-1758 > URL: https://issues.jboss.org/browse/ARQ-1758 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Robert Panzer > Attachments: debug.png > > > I have an erronous test class that cannot be loaded in the container due to a NoClassDefFoundError. (A dependent class is missing.) > The test passes unexpectedly and all test methods are reported to have passed although log entries or SystemOuts show that the methods are actually never invoked. > The problem seems to be a regression that came with the last release. > In JUnitTestRunner the TestResults exception is overwritten with null in such a case. > I will attach a screenshot of the debugger showing that. > I also have a try of a patch that I will link as soon as I prepared the pull request on github. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 17:10:38 2014 From: issues at jboss.org (Rich DiCroce (JIRA)) Date: Wed, 11 Jun 2014 17:10:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1796) Regression: JUnit ExpectedException is not handled correctly In-Reply-To: References: Message-ID: Rich DiCroce created ARQ-1796: --------------------------------- Summary: Regression: JUnit ExpectedException is not handled correctly Key: ARQ-1796 URL: https://issues.jboss.org/browse/ARQ-1796 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.1.4.Final Reporter: Rich DiCroce I have many tests using JUnit's ExcpectedException rule. In Arquillian 1.1.3, these tests worked perfectly. When I tried to update to 1.1.4, they broke. It seems like Arquillian now catches the exceptions before ExpectedException does, and propagates them back to the client. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 18:47:39 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 11 Jun 2014 18:47:39 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1796) Regression: JUnit ExpectedException is not handled correctly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1796: ------------------------------- Fix Version/s: 1.1.5.Final > Regression: JUnit ExpectedException is not handled correctly > ------------------------------------------------------------ > > Key: ARQ-1796 > URL: https://issues.jboss.org/browse/ARQ-1796 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Rich DiCroce > Fix For: 1.1.5.Final > > > I have many tests using JUnit's ExcpectedException rule. In Arquillian 1.1.3, these tests worked perfectly. When I tried to update to 1.1.4, they broke. It seems like Arquillian now catches the exceptions before ExpectedException does, and propagates them back to the client. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 18:49:38 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 11 Jun 2014 18:49:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1758) Test passes although it fails unexpectedly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1758: ------------------------------- Fix Version/s: 1.1.5.Final > Test passes although it fails unexpectedly > ------------------------------------------ > > Key: ARQ-1758 > URL: https://issues.jboss.org/browse/ARQ-1758 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Robert Panzer > Fix For: 1.1.5.Final > > Attachments: debug.png > > > I have an erronous test class that cannot be loaded in the container due to a NoClassDefFoundError. (A dependent class is missing.) > The test passes unexpectedly and all test methods are reported to have passed although log entries or SystemOuts show that the methods are actually never invoked. > The problem seems to be a regression that came with the last release. > In JUnitTestRunner the TestResults exception is overwritten with null in such a case. > I will attach a screenshot of the debugger showing that. > I also have a try of a patch that I will link as soon as I prepared the pull request on github. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 07:37:40 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 12 Jun 2014 07:37:40 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-451) Create job for publishing Graphene 2.1.0-SNAPSHOT to the public repository In-Reply-To: References: Message-ID: Juraj H?ska created ARQGRA-451: ---------------------------------- Summary: Create job for publishing Graphene 2.1.0-SNAPSHOT to the public repository Key: ARQGRA-451 URL: https://issues.jboss.org/browse/ARQGRA-451 Project: Arquillian Graphene Issue Type: Task Components: build Affects Versions: 2.1.0.Alpha1 Reporter: Juraj H?ska Please set up Jenkins job for continuous delivery of Graphene 2.1.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 07:39:38 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 12 Jun 2014 07:39:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-451) Create job for publishing Graphene 2.1.0-SNAPSHOT to the public repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska reassigned ARQGRA-451: ---------------------------------- Assignee: Juraj H?ska > Create job for publishing Graphene 2.1.0-SNAPSHOT to the public repository > -------------------------------------------------------------------------- > > Key: ARQGRA-451 > URL: https://issues.jboss.org/browse/ARQGRA-451 > Project: Arquillian Graphene > Issue Type: Task > Components: build > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > Please set up Jenkins job for continuous delivery of Graphene 2.1.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 07:51:39 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 12 Jun 2014 07:51:39 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-451) Create job for publishing Graphene 2.1.0-SNAPSHOT to the public repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQGRA-451 started by Juraj H?ska. > Create job for publishing Graphene 2.1.0-SNAPSHOT to the public repository > -------------------------------------------------------------------------- > > Key: ARQGRA-451 > URL: https://issues.jboss.org/browse/ARQGRA-451 > Project: Arquillian Graphene > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > Please set up Jenkins job for continuous delivery of Graphene 2.1.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 08:03:39 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 12 Jun 2014 08:03:39 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1793) Release new version of arquillian-weld-ee-embedded with cdi-api 1.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1793: ------------------------------- Component/s: Weld Containers (was: Deployable Containers SPI) > Release new version of arquillian-weld-ee-embedded with cdi-api 1.2 > ------------------------------------------------------------------- > > Key: ARQ-1793 > URL: https://issues.jboss.org/browse/ARQ-1793 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR8 > Reporter: Tomas Remes > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 08:10:38 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 12 Jun 2014 08:10:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1793) arquillian-weld-ee-embedded expose wrong version of Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1793: ------------------------------- Summary: arquillian-weld-ee-embedded expose wrong version of Arquillian (was: Release new version of arquillian-weld-ee-embedded with cdi-api 1.2) > arquillian-weld-ee-embedded expose wrong version of Arquillian > -------------------------------------------------------------- > > Key: ARQ-1793 > URL: https://issues.jboss.org/browse/ARQ-1793 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR8 > Reporter: Tomas Remes > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 08:12:38 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 12 Jun 2014 08:12:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1793) arquillian-weld-ee-embedded expose wrong version of Arquillian Core In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1793: ------------------------------- Summary: arquillian-weld-ee-embedded expose wrong version of Arquillian Core (was: arquillian-weld-ee-embedded expose wrong version of Arquillian) > arquillian-weld-ee-embedded expose wrong version of Arquillian Core > ------------------------------------------------------------------- > > Key: ARQ-1793 > URL: https://issues.jboss.org/browse/ARQ-1793 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR8 > Reporter: Tomas Remes > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 08:12:39 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 12 Jun 2014 08:12:39 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1793) arquillian-weld-ee-embedded expose wrong version of Arquillian Core In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1793: ------------------------------- Description: weld-bom expose an older v of Arquillian Core via weld-parent. This forces the direct dependencies of arquillian-weld-ee-embedded on Arquillian Core to downgrade to the weld-bom v while leaving the other dependencies upgraded. Result is a mixed set of Arquillian Core artifacts. > arquillian-weld-ee-embedded expose wrong version of Arquillian Core > ------------------------------------------------------------------- > > Key: ARQ-1793 > URL: https://issues.jboss.org/browse/ARQ-1793 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR8 > Reporter: Tomas Remes > > weld-bom expose an older v of Arquillian Core via weld-parent. This forces the direct dependencies of arquillian-weld-ee-embedded on Arquillian Core to downgrade to the weld-bom v while leaving the other dependencies upgraded. Result is a mixed set of Arquillian Core artifacts. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 12:05:38 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 12 Jun 2014 12:05:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1793) arquillian-weld-ee-embedded expose wrong version of Arquillian Core In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1793: ------------------------------- Fix Version/s: weld_1.0.0.Final > arquillian-weld-ee-embedded expose wrong version of Arquillian Core > ------------------------------------------------------------------- > > Key: ARQ-1793 > URL: https://issues.jboss.org/browse/ARQ-1793 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR8 > Reporter: Tomas Remes > Fix For: weld_1.0.0.Final > > > weld-bom expose an older v of Arquillian Core via weld-parent. This forces the direct dependencies of arquillian-weld-ee-embedded on Arquillian Core to downgrade to the weld-bom v while leaving the other dependencies upgraded. Result is a mixed set of Arquillian Core artifacts. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 12:05:39 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 12 Jun 2014 12:05:39 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1793) arquillian-weld-ee-embedded expose wrong version of Arquillian Core In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1793. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-container-weld/commit/f10efb01c3be8cfa86afc6f0f54059ddca7cf3bb > arquillian-weld-ee-embedded expose wrong version of Arquillian Core > ------------------------------------------------------------------- > > Key: ARQ-1793 > URL: https://issues.jboss.org/browse/ARQ-1793 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR8 > Reporter: Tomas Remes > Assignee: Aslak Knutsen > Fix For: weld_1.0.0.Final > > > weld-bom expose an older v of Arquillian Core via weld-parent. This forces the direct dependencies of arquillian-weld-ee-embedded on Arquillian Core to downgrade to the weld-bom v while leaving the other dependencies upgraded. Result is a mixed set of Arquillian Core artifacts. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 02:52:38 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 13 Jun 2014 02:52:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-451) Create job for publishing Graphene 2.1.0-SNAPSHOT to the public repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska resolved ARQGRA-451. -------------------------------- Resolution: Done Graphene 2.1.x is now published to JBoss Snapshots on a daily basis. > Create job for publishing Graphene 2.1.0-SNAPSHOT to the public repository > -------------------------------------------------------------------------- > > Key: ARQGRA-451 > URL: https://issues.jboss.org/browse/ARQGRA-451 > Project: Arquillian Graphene > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > Please set up Jenkins job for continuous delivery of Graphene 2.1.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 05:59:38 2014 From: issues at jboss.org (Jakub Cechacek (JIRA)) Date: Fri, 13 Jun 2014 05:59:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-452) Allow screenshooter configuration to be locally overridden In-Reply-To: References: Message-ID: Jakub Cechacek created ARQGRA-452: ------------------------------------- Summary: Allow screenshooter configuration to be locally overridden Key: ARQGRA-452 URL: https://issues.jboss.org/browse/ARQGRA-452 Project: Arquillian Graphene Issue Type: Enhancement Security Level: Public (Everyone can see) Components: screenshooter Reporter: Jakub Cechacek Priority: Optional Currently the configuration of Screenshooter is done globally inside arquillian.xml. It would be useful to provide a way how to change this configuration locally for specific class. Example: arquillian xml: {code} false false false true {code} This configuration is sufficient for the majority of my tests. However then there are those few complicated / unstable tests for which I would like to take more screenshots. AFAIK there is no way how to change the configuration only for these tests. Nice solution would be to provide an annotation which will allow you to change the configuration. Something like {code} @Screenshot(onEveryAction=true, afterTest=True, beforeTest=True) public class MyUnstableTestCase() {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 06:01:48 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 13 Jun 2014 06:01:48 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-452) Allow screenshooter configuration to be locally overridden In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQGRA-452: ------------------------------------- Affects Version/s: 2.1.0.Alpha1 > Allow screenshooter configuration to be locally overridden > ----------------------------------------------------------- > > Key: ARQGRA-452 > URL: https://issues.jboss.org/browse/ARQGRA-452 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1-Tracking > Reporter: Jakub Cechacek > Priority: Optional > > Currently the configuration of Screenshooter is done globally inside arquillian.xml. It would be useful to provide a way how to change this configuration locally for specific class. > Example: > arquillian xml: > {code} > false > false > false > true > {code} > This configuration is sufficient for the majority of my tests. However then there are those few complicated / unstable tests for which I would like to take more screenshots. AFAIK there is no way how to change the configuration only for these tests. > Nice solution would be to provide an annotation which will allow you to change the configuration. Something like > {code} > @Screenshot(onEveryAction=true, afterTest=True, beforeTest=True) > public class MyUnstableTestCase() > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 06:01:48 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 13 Jun 2014 06:01:48 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-452) Allow screenshooter configuration to be locally overridden In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQGRA-452: ------------------------------------- Affects Version/s: 2.1-Tracking (was: 2.1.0.Alpha1) > Allow screenshooter configuration to be locally overridden > ----------------------------------------------------------- > > Key: ARQGRA-452 > URL: https://issues.jboss.org/browse/ARQGRA-452 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1-Tracking > Reporter: Jakub Cechacek > Priority: Optional > > Currently the configuration of Screenshooter is done globally inside arquillian.xml. It would be useful to provide a way how to change this configuration locally for specific class. > Example: > arquillian xml: > {code} > false > false > false > true > {code} > This configuration is sufficient for the majority of my tests. However then there are those few complicated / unstable tests for which I would like to take more screenshots. AFAIK there is no way how to change the configuration only for these tests. > Nice solution would be to provide an annotation which will allow you to change the configuration. Something like > {code} > @Screenshot(onEveryAction=true, afterTest=True, beforeTest=True) > public class MyUnstableTestCase() > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 06:01:48 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 13 Jun 2014 06:01:48 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-452) Allow screenshooter configuration to be locally overridden In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQGRA-452: ---------------------------------------- Assignee: Stefan Miklosovic > Allow screenshooter configuration to be locally overridden > ----------------------------------------------------------- > > Key: ARQGRA-452 > URL: https://issues.jboss.org/browse/ARQGRA-452 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1-Tracking > Reporter: Jakub Cechacek > Assignee: Stefan Miklosovic > Priority: Optional > > Currently the configuration of Screenshooter is done globally inside arquillian.xml. It would be useful to provide a way how to change this configuration locally for specific class. > Example: > arquillian xml: > {code} > false > false > false > true > {code} > This configuration is sufficient for the majority of my tests. However then there are those few complicated / unstable tests for which I would like to take more screenshots. AFAIK there is no way how to change the configuration only for these tests. > Nice solution would be to provide an annotation which will allow you to change the configuration. Something like > {code} > @Screenshot(onEveryAction=true, afterTest=True, beforeTest=True) > public class MyUnstableTestCase() > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 06:05:38 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 13 Jun 2014 06:05:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-452) Allow screenshooter configuration to be locally overridden In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975938#comment-12975938 ] Stefan Miklosovic commented on ARQGRA-452: ------------------------------------------ What kind of strategy do you want to use here when you put @Screenshot annotation on a method? That screenshot annotation has to have some default values. It is clear that specified parameter to that annotation overrides settings in arquillian.xml. In case that property is not specified there, what setting should "win"? Annotation one which is not specified explicitly or property in arq.xml ? > Allow screenshooter configuration to be locally overridden > ----------------------------------------------------------- > > Key: ARQGRA-452 > URL: https://issues.jboss.org/browse/ARQGRA-452 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1-Tracking > Reporter: Jakub Cechacek > Assignee: Stefan Miklosovic > Priority: Optional > > Currently the configuration of Screenshooter is done globally inside arquillian.xml. It would be useful to provide a way how to change this configuration locally for specific class. > Example: > arquillian xml: > {code} > false > false > false > true > {code} > This configuration is sufficient for the majority of my tests. However then there are those few complicated / unstable tests for which I would like to take more screenshots. AFAIK there is no way how to change the configuration only for these tests. > Nice solution would be to provide an annotation which will allow you to change the configuration. Something like > {code} > @Screenshot(onEveryAction=true, afterTest=True, beforeTest=True) > public class MyUnstableTestCase() > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 06:11:38 2014 From: issues at jboss.org (Jakub Cechacek (JIRA)) Date: Fri, 13 Jun 2014 06:11:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-452) Allow screenshooter configuration to be locally overridden In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975939#comment-12975939 ] Jakub Cechacek commented on ARQGRA-452: --------------------------------------- I would see the precedence as follows: # Explicit Annotation param values # Explicit arquillian.xml property values # Implicit Annotation values (which I believe should be the same as default property values) # Default property values > Allow screenshooter configuration to be locally overridden > ----------------------------------------------------------- > > Key: ARQGRA-452 > URL: https://issues.jboss.org/browse/ARQGRA-452 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1-Tracking > Reporter: Jakub Cechacek > Assignee: Stefan Miklosovic > Priority: Optional > > Currently the configuration of Screenshooter is done globally inside arquillian.xml. It would be useful to provide a way how to change this configuration locally for specific class. > Example: > arquillian xml: > {code} > false > false > false > true > {code} > This configuration is sufficient for the majority of my tests. However then there are those few complicated / unstable tests for which I would like to take more screenshots. AFAIK there is no way how to change the configuration only for these tests. > Nice solution would be to provide an annotation which will allow you to change the configuration. Something like > {code} > @Screenshot(onEveryAction=true, afterTest=True, beforeTest=True) > public class MyUnstableTestCase() > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 06:13:38 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 13 Jun 2014 06:13:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1797) Allow screenshooter configuration to be locally overridden In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska moved ARQGRA-452 to ARQ-1797: ----------------------------------------- Project: Arquillian (was: Arquillian Graphene) Key: ARQ-1797 (was: ARQGRA-452) Affects Version/s: recorder_1.0.0.Alpha3 (was: 2.1-Tracking) Component/s: Extension - Recorder (was: screenshooter) > Allow screenshooter configuration to be locally overridden > ----------------------------------------------------------- > > Key: ARQ-1797 > URL: https://issues.jboss.org/browse/ARQ-1797 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Jakub Cechacek > Assignee: Stefan Miklosovic > Priority: Optional > > Currently the configuration of Screenshooter is done globally inside arquillian.xml. It would be useful to provide a way how to change this configuration locally for specific class. > Example: > arquillian xml: > {code} > false > false > false > true > {code} > This configuration is sufficient for the majority of my tests. However then there are those few complicated / unstable tests for which I would like to take more screenshots. AFAIK there is no way how to change the configuration only for these tests. > Nice solution would be to provide an annotation which will allow you to change the configuration. Something like > {code} > @Screenshot(onEveryAction=true, afterTest=True, beforeTest=True) > public class MyUnstableTestCase() > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 06:27:38 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jun 2014 06:27:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-449: ------------------------------ Description: This code: {code} @Test public void nativeViewTest() { driver.switchTo().window("NATIVE_APP"); } {code} That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. It produces this exception: {code} java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) at com.sun.proxy.$Proxy27.window(Unknown Source) at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) {code} was: This code: {code} @Test public void nativeViewTest() { driver.switchTo().window("NATIVE_APP"); } {code} That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. It produces this exception: java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) at com.sun.proxy.$Proxy27.window(Unknown Source) at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > {code} > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 06:27:39 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jun 2014 06:27:39 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975946#comment-12975946 ] Luk?? Fry? commented on ARQGRA-449: ----------------------------------- Had you chance to try yet, [~smikloso]? > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > {code} > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 07:00:43 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 13 Jun 2014 07:00:43 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-453) takeOnEveryAction acts only on methods on WebDriver object, add support for PO & PF & WebElement In-Reply-To: References: Message-ID: Juraj H?ska created ARQGRA-453: ---------------------------------- Summary: takeOnEveryAction acts only on methods on 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 Security Level: Public (Everyone can see) Components: screenshooter Affects Versions: 2.1.0.Alpha1 Reporter: Juraj H?ska {{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.2.6#6264) From issues at jboss.org Fri Jun 13 07:00:43 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 13 Jun 2014 07:00:43 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-453) takeOnEveryAction acts only on methods on 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 ] Juraj H?ska updated ARQGRA-453: ------------------------------- Component/s: core > takeOnEveryAction acts only on methods on 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 > Security Level: Public(Everyone can see) > Components: core, screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > > {{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.2.6#6264) From issues at jboss.org Fri Jun 13 07:02:38 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 13 Jun 2014 07:02:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-453) takeOnEveryAction acts only on methods on 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:comment-tabpanel&focusedCommentId=12975959#comment-12975959 ] Juraj H?ska commented on ARQGRA-453: ------------------------------------ As we already discuss with [~lfryc], to support this feature, core Graphene would need to implement inheritance of the interceptors. So for example when you register interceptor on a Page Object it will be propagated to all its {{WebElement}}s and other PO and PF. > takeOnEveryAction acts only on methods on 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 > Security Level: Public(Everyone can see) > Components: core, screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > > {{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.2.6#6264) From issues at jboss.org Fri Jun 13 07:02:38 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 13 Jun 2014 07:02:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-453) takeOnEveryAction acts only on methods on 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:comment-tabpanel&focusedCommentId=12975959#comment-12975959 ] Juraj H?ska edited comment on ARQGRA-453 at 6/13/14 7:02 AM: ------------------------------------------------------------- As we already discuss with [~lfryc], to support this feature, core Graphene would need to implement inheritance of the interceptors. So for example when you register interceptor on a Page Object it will be propagated to all its {{WebElement}} s and other PO and PF. was (Author: jhuska): As we already discuss with [~lfryc], to support this feature, core Graphene would need to implement inheritance of the interceptors. So for example when you register interceptor on a Page Object it will be propagated to all its {{WebElement}}s and other PO and PF. > takeOnEveryAction acts only on methods on 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 > Security Level: Public(Everyone can see) > Components: core, screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > > {{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.2.6#6264) From issues at jboss.org Fri Jun 13 07:04:38 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 13 Jun 2014 07:04:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-453) takeOnEveryAction acts only on methods on 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 ] Juraj H?ska reassigned ARQGRA-453: ---------------------------------- Assignee: Juraj H?ska > takeOnEveryAction acts only on methods on 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 > Security Level: Public(Everyone can see) > Components: core, screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > {{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.2.6#6264) From issues at jboss.org Fri Jun 13 07:04:39 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 13 Jun 2014 07:04:39 -0400 (EDT) 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 ] Juraj H?ska updated ARQGRA-453: ------------------------------- Summary: takeOnEveryAction acts only on methods from WebDriver object, add support for PO & PF & WebElement (was: takeOnEveryAction acts only on methods on WebDriver object, add support for PO & PF & WebElement) > 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 > Security Level: Public(Everyone can see) > Components: core, screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > {{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.2.6#6264) From issues at jboss.org Fri Jun 13 07:04:39 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 13 Jun 2014 07:04:39 -0400 (EDT) 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:comment-tabpanel&focusedCommentId=12975959#comment-12975959 ] Juraj H?ska edited comment on ARQGRA-453 at 6/13/14 7:03 AM: ------------------------------------------------------------- As we already discuss with [~lfryc], to support this feature, core Graphene would need to implement inheritance of the interceptors. So for example when you register interceptor on a Page Object it will be propagated to all its {{WebElement}} s and other POs and PFs defined in that parent PO. was (Author: jhuska): As we already discuss with [~lfryc], to support this feature, core Graphene would need to implement inheritance of the interceptors. So for example when you register interceptor on a Page Object it will be propagated to all its {{WebElement}} s and other PO and PF. > 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 > Security Level: Public(Everyone can see) > Components: core, screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > {{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.2.6#6264) From issues at jboss.org Fri Jun 13 08:00:46 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 13 Jun 2014 08:00:46 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975977#comment-12975977 ] Stefan Miklosovic commented on ARQGRA-449: ------------------------------------------ [~lfryc] I put breakpoint here (1) and here (2) and exception is throw here (3). It is one of these below, they are in ancillaryTypes variable on line 166. Do you know how to check it fast? I was not able to dig into it any furter, I was not able to attach sources for that sun.misc proxy generator classes .... interface org.openqa.selenium.JavascriptExecutor, interface org.openqa.selenium.ContextAware, interface org.openqa.selenium.internal.FindsByCssSelector, interface org.openqa.selenium.WebDriver, interface org.openqa.selenium.internal.FindsByName, interface org.openqa.selenium.Rotatable, interface org.openqa.selenium.interactions.HasInputDevices, interface org.openqa.selenium.internal.FindsByXPath, interface org.openqa.selenium.interactions.HasTouchScreen, interface org.openqa.selenium.internal.FindsByLinkText, interface io.selendroid.ScreenBrightness, interface io.selendroid.Configuration, interface org.openqa.selenium.HasCapabilities, interface org.openqa.selenium.internal.FindsById, interface io.selendroid.HasAirplaneMode, interface org.openqa.selenium.internal.FindsByClassName, interface io.selendroid.AdbSupport, interface org.openqa.selenium.TakesScreenshot, interface org.openqa.selenium.internal.FindsByTagName, interface org.jboss.arquillian.graphene.proxy.GrapheneProxyInstance (1) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/proxy/GrapheneProxy.java#L91 (2) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/proxy/GrapheneProxy.java#L92 (3) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/proxy/GrapheneProxy.java#L166 > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > {code} > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 08:06:38 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 13 Jun 2014 08:06:38 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975979#comment-12975979 ] Stefan Miklosovic commented on ARQGRA-449: ------------------------------------------ got it ... https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/proxy/GrapheneProxyInstance.java#L46 https://github.com/SeleniumHQ/selenium/blob/master/java/client/src/org/openqa/selenium/ContextAware.java Do we rename that GrapheneProxyInstance method? > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > {code} > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 14 10:12:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Sat, 14 Jun 2014 10:12:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-450) takeBeforeTest does not work when loading of the page is in JUnit @Before method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-450: ------------------------------- Summary: takeBeforeTest does not work when loading of the page is in JUnit @Before method (was: takeBeforeTest takes screenshot only for first test when loading of page is done in @Before) > takeBeforeTest does not work when loading of the page is in JUnit @Before method > -------------------------------------------------------------------------------- > > Key: ARQGRA-450 > URL: https://issues.jboss.org/browse/ARQGRA-450 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > {{takeBeforeTest}} option is broken, because when there are multiple tests, and the loading of the page is done on {{@Before}} method, then screenshot is taken only for first test. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 14 10:26:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Sat, 14 Jun 2014 10:26:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-450) takeBeforeTest does not work when loading of the page is in JUnit @Before method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-450: ------------------------------- Description: {{takeBeforeTest}} option is broken, because when there are multiple tests, and the loading of the page is done on {{@Before}} method, then the first test is omitted. It is because JUnit @Before observer is called before the Graphene Screenshooter one, thus the registration of interceptor which takes screenshots is done quite late. was:{{takeBeforeTest}} option is broken, because when there are multiple tests, and the loading of the page is done on {{@Before}} method, then screenshot is taken only for first test. > takeBeforeTest does not work when loading of the page is in JUnit @Before method > -------------------------------------------------------------------------------- > > Key: ARQGRA-450 > URL: https://issues.jboss.org/browse/ARQGRA-450 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > {{takeBeforeTest}} option is broken, because when there are multiple tests, and the loading of the page is done on {{@Before}} method, then the first test is omitted. > It is because JUnit @Before observer is called before the Graphene Screenshooter one, thus the registration of interceptor which takes screenshots is done quite late. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 14 10:32:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Sat, 14 Jun 2014 10:32:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-450) takeBeforeTest does not work when loading of the page is in JUnit @Before method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976312#comment-12976312 ] Juraj H?ska commented on ARQGRA-450: ------------------------------------ Just a note that it works correctly with @InitialPage Graphene feature. > takeBeforeTest does not work when loading of the page is in JUnit @Before method > -------------------------------------------------------------------------------- > > Key: ARQGRA-450 > URL: https://issues.jboss.org/browse/ARQGRA-450 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > {{takeBeforeTest}} option is broken, because when there are multiple tests, and the loading of the page is done on {{@Before}} method, then the first test is omitted. > It is because JUnit @Before observer is called before the Graphene Screenshooter one, thus the registration of interceptor which takes screenshots is done quite late. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 15 05:27:24 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Sun, 15 Jun 2014 05:27:24 -0400 (EDT) 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? reassigned ARQGRA-86: -------------------------------- Assignee: Juraj H?ska (was: Luk?? Fry?) > Support XHR Halter > ------------------ > > Key: ARQGRA-86 > URL: https://issues.jboss.org/browse/ARQGRA-86 > Project: Arquillian Graphene > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 2.1-Tracking > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 15 05:29:24 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Sun, 15 Jun 2014 05:29:24 -0400 (EDT) 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: ------------------------------ Assignee: (was: Luk?? Fry?) > 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 > Security Level: Public(Everyone can see) > 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.2.6#6264) From issues at jboss.org Sun Jun 15 23:35:24 2014 From: issues at jboss.org (Chris Jones (JIRA)) Date: Sun, 15 Jun 2014 23:35:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Jones updated ARQGRA-446: ------------------------------- Attachment: groovy-page-support.patch Patch for groovy page objects > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Attachments: graphene-groovy-test.zip, groovy-page-support.patch > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 00:09:24 2014 From: issues at jboss.org (Chris Jones (JIRA)) Date: Mon, 16 Jun 2014 00:09:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Jones updated ARQGRA-446: ------------------------------- Attachment: groovy-page-support (fixed paths).patch Updating patch, fixed base path > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Attachments: graphene-groovy-test.zip, groovy-page-support (fixed paths).patch, groovy-page-support.patch > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 09:14:24 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jun 2014 09:14:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976559#comment-12976559 ] Luk?? Fry? commented on ARQGRA-449: ----------------------------------- +1 for renaming our method #getContext to #getGrapheneContext. Is just needs to be renamed in whole project. > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > {code} > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 09:57:24 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jun 2014 09:57:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-449: ------------------------------ Fix Version/s: 2.0.4.Final > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > Fix For: 2.0.4.Final > > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > {code} > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 09:57:25 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jun 2014 09:57:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-449: ------------------------------ Assignee: Stefan Miklosovic > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: 2.0.4.Final > > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > {code} > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 10:09:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 16 Jun 2014 10:09:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQGRA-449: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/112 > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: 2.0.4.Final > > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > {code} > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 10:45:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jun 2014 10:45:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976621#comment-12976621 ] Luk?? Fry? commented on ARQGRA-446: ----------------------------------- Nice, seems valid. Chris, do you want me to apply this patch or could you open the pull request against Graphene? https://github.com/arquillian/arquillian-graphene/blob/master/CONTRIBUTING.md I can do it for you, just let me know; but if you have GitHub account and would you like to have your contribution in... > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Attachments: graphene-groovy-test.zip, groovy-page-support (fixed paths).patch, groovy-page-support.patch > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 11:03:24 2014 From: issues at jboss.org (Chris Jones (JIRA)) Date: Mon, 16 Jun 2014 11:03:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976635#comment-12976635 ] Chris Jones commented on ARQGRA-446: ------------------------------------ You can handle it thanks > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Attachments: graphene-groovy-test.zip, groovy-page-support (fixed paths).patch, groovy-page-support.patch > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 11:05:25 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jun 2014 11:05:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-446: ------------------------------ Status: Pull Request Sent (was: Open) the patch is attached > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Attachments: graphene-groovy-test.zip, groovy-page-support (fixed paths).patch, groovy-page-support.patch > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 05:31:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 17 Jun 2014 05:31:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-450) takeBeforeTest does not work when loading of the page is in JUnit @Before method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska resolved ARQGRA-450. -------------------------------- Resolution: Done Fixed with [this|https://github.com/arquillian/arquillian-graphene/commit/f5d63ad4ba69346908ddd425e21d4a38c80ed1d6] commit. Increased the precedence for Before event observer. > takeBeforeTest does not work when loading of the page is in JUnit @Before method > -------------------------------------------------------------------------------- > > Key: ARQGRA-450 > URL: https://issues.jboss.org/browse/ARQGRA-450 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > {{takeBeforeTest}} option is broken, because when there are multiple tests, and the loading of the page is done on {{@Before}} method, then the first test is omitted. > It is because JUnit @Before observer is called before the Graphene Screenshooter one, thus the registration of interceptor which takes screenshots is done quite late. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 23:35:24 2014 From: issues at jboss.org (Stephen Coy (JIRA)) Date: Tue, 17 Jun 2014 23:35:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-866) Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Coy updated ARQ-866: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-tomcat/pull/24 This adds support in the TC6 container. Note that I'm actively using this. > Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > ------------------------------------------------------------------------------------------------- > > Key: ARQ-866 > URL: https://issues.jboss.org/browse/ARQ-866 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR3 > Reporter: Dan Allen > > The Tomcat managed container adapter assumes that catalina.base is the same as catalina.home. > {code} > String absolutePath = new File(CATALINA_HOME).getAbsolutePath(); > ... > cmd.add("-Dcatalina.base=" + absolutePath); > cmd.add("-Dcatalina.home=" + absolutePath); > {code} > However, this is not necessary true. For instance, when using Tomcat from Eclipse, the catalina.base (which includes the configuration files) is managed inside the Eclipse workspace. This allows the developer to modify Tomcat settings without affecting the system installation. > The fix for this problem is to add a configuration property named "catalinaBase" and honor if it's set when building the startup script. > This affects all the Tomcat managed containers (5, 6 and 7). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 04:13:25 2014 From: issues at jboss.org (Sueleyman Vurucu (JIRA)) Date: Wed, 18 Jun 2014 04:13:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1798) Shrinkwrap maven local repo resolution not working since ARQ 1.1.4.Final In-Reply-To: References: Message-ID: Sueleyman Vurucu created ARQ-1798: ------------------------------------- Summary: Shrinkwrap maven local repo resolution not working since ARQ 1.1.4.Final Key: ARQ-1798 URL: https://issues.jboss.org/browse/ARQ-1798 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Maven Plugin Affects Versions: 1.1.4.Final Environment: Maven 3.2.1 Java 7 64 - bit Windows 7 64 bit Reporter: Sueleyman Vurucu Assignee: Davide D'Alto I update ARQ from 1.1.3.Final to 1.1.4.Final. After I try to excecute my testsuite I had a Exception that some of the artifacts could not be resolved. After Debugging I see that shrinkwrap looks for that artifacts on our local nexus server. Unfortunately we dont deploy our development artifact on nexus. The MavenResolverSystem is configured like shown below: // ARQ 1.1.3.Final private static MavenResolverSystem getMavenDependencyResolver() { MavenResolverSystem mavenResolverSystem = Maven.configureResolver().fromFile(pathToSettingsXML); mavenResolverSystem.offline(); return mavenResolverSystem; } // ARQ 1.1.4.Final private static ConfigurableMavenResolverSystem getMavenDependencyResolver() { ConfigurableMavenResolverSystem mavenResolverSystem = Resolvers.configure(ConfigurableMavenResolverSystem.class); mavenResolverSystem.withClassPathResolution(true); mavenResolverSystem.fromFile(pathToSettingsXML); mavenResolverSystem.workOffline(); return mavenResolverSystem; } As you can see I say to MavenResolverSystem that it should work offline. After deep debugging I see that the resolversystem try to find all the artifacts on our nexus. //ARQ 1.1.3.Final DefaultRepositorySystem:367 com.siemag.base:wms-base-controller:ejb:3.0.0-SNAPSHOT <(compile) //ARQ 1.1.4.Final In the class DefaultRepositorySystem:367 com.siemag.base:wms-base-controller:ejb:3.0.0-SNAPSHOT < [nexus (http://172.16.55.1:8081/nexus/content/groups/public, releases)] -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 06:43:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 18 Jun 2014 06:43:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1191) Tomcat Embedded 6 undeploy(archive) issue In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1191: ------------------------------- Fix Version/s: tomcat_1.0.0.Final > Tomcat Embedded 6 undeploy(archive) issue > ----------------------------------------- > > Key: ARQ-1191 > URL: https://issues.jboss.org/browse/ARQ-1191 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR4 > Environment: Tomcat-embedded-6 > Reporter: George Vagenas > Priority: Critical > Fix For: tomcat_1.0.0.Final > > Attachments: arquillian-container-tomcat.patch, SimpleArqTest.zip > > > Having two test classes that extend an abstract class that provides the deployment archive (actually the fact that they extend an abstract class is insignificant, the important point here is that the deployment archive name is the same). > When the test classes run individually pass the test. When these two test classes combined in a test suite, the first only pass and the second always fails. > @RunWith(Suite.class) > @SuiteClasses({ > RegisteredEchoServletTestCase.class, > RegisteredEchoServletTestCase2.class > }) > public class MyTestSuite { > } > Find attached @RunWith(Suite.class) > @SuiteClasses({ > RegisteredEchoServletTestCase.class, > RegisteredEchoServletTestCase2.class > }) > public class MyTestSuite { > } > Issue exists only on tomcat 6 container. I run the same test suite against tomcat-embedded-7 with success. > George -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 06:45:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 18 Jun 2014 06:45:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1799) Remove dependency on common-codecs In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1799: ---------------------------------- Summary: Remove dependency on common-codecs Key: ARQ-1799 URL: https://issues.jboss.org/browse/ARQ-1799 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR6 Reporter: Aslak Knutsen Since client side can depend on Common-Codec and cause version conflicts with the Container, remove the external dependency and move Base64 encoding class internally. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 06:45:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 18 Jun 2014 06:45:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1799) Remove dependency on common-codecs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1799: ------------------------------- Fix Version/s: tomcat_1.0.0.Final > Remove dependency on common-codecs > ---------------------------------- > > Key: ARQ-1799 > URL: https://issues.jboss.org/browse/ARQ-1799 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Reporter: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > Since client side can depend on Common-Codec and cause version conflicts with the Container, remove the external dependency and move Base64 encoding class internally. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 06:49:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 18 Jun 2014 06:49:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1799) Remove dependency on common-codecs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1799. -------------------------------- Assignee: Aslak Knutsen Resolution: Done > Remove dependency on common-codecs > ---------------------------------- > > Key: ARQ-1799 > URL: https://issues.jboss.org/browse/ARQ-1799 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > Since client side can depend on Common-Codec and cause version conflicts with the Container, remove the external dependency and move Base64 encoding class internally. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 06:49:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 18 Jun 2014 06:49:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1191) Tomcat Embedded 6 undeploy(archive) issue In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1191. -------------------------------- Assignee: Aslak Knutsen Resolution: Done > Tomcat Embedded 6 undeploy(archive) issue > ----------------------------------------- > > Key: ARQ-1191 > URL: https://issues.jboss.org/browse/ARQ-1191 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR4 > Environment: Tomcat-embedded-6 > Reporter: George Vagenas > Assignee: Aslak Knutsen > Priority: Critical > Fix For: tomcat_1.0.0.Final > > Attachments: arquillian-container-tomcat.patch, SimpleArqTest.zip > > > Having two test classes that extend an abstract class that provides the deployment archive (actually the fact that they extend an abstract class is insignificant, the important point here is that the deployment archive name is the same). > When the test classes run individually pass the test. When these two test classes combined in a test suite, the first only pass and the second always fails. > @RunWith(Suite.class) > @SuiteClasses({ > RegisteredEchoServletTestCase.class, > RegisteredEchoServletTestCase2.class > }) > public class MyTestSuite { > } > Find attached @RunWith(Suite.class) > @SuiteClasses({ > RegisteredEchoServletTestCase.class, > RegisteredEchoServletTestCase2.class > }) > public class MyTestSuite { > } > Issue exists only on tomcat 6 container. I run the same test suite against tomcat-embedded-7 with success. > George -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 06:49:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 18 Jun 2014 06:49:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-701) Tomcat containers are not able to start after begin stop (AddressAlready in use) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-701. ------------------------------- Assignee: Aslak Knutsen Resolution: Done > Tomcat containers are not able to start after begin stop (AddressAlready in use) > -------------------------------------------------------------------------------- > > Key: ARQ-701 > URL: https://issues.jboss.org/browse/ARQ-701 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR2 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > Setting a embedded Tomcat 7 container to manual control mode and calling, start/stop/start cause Address Already in use Exception. > stop should call tomcat.destroy > (possible other tomcat versions as well, investigate) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 07:51:24 2014 From: issues at jboss.org (Stephen Coy (JIRA)) Date: Wed, 18 Jun 2014 07:51:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-866) Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977334#comment-12977334 ] Stephen Coy commented on ARQ-866: --------------------------------- Support for TC 5.5 and TC 7 now included > Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > ------------------------------------------------------------------------------------------------- > > Key: ARQ-866 > URL: https://issues.jboss.org/browse/ARQ-866 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR3 > Reporter: Dan Allen > > The Tomcat managed container adapter assumes that catalina.base is the same as catalina.home. > {code} > String absolutePath = new File(CATALINA_HOME).getAbsolutePath(); > ... > cmd.add("-Dcatalina.base=" + absolutePath); > cmd.add("-Dcatalina.home=" + absolutePath); > {code} > However, this is not necessary true. For instance, when using Tomcat from Eclipse, the catalina.base (which includes the configuration files) is managed inside the Eclipse workspace. This allows the developer to modify Tomcat settings without affecting the system installation. > The fix for this problem is to add a configuration property named "catalinaBase" and honor if it's set when building the startup script. > This affects all the Tomcat managed containers (5, 6 and 7). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 08:45:24 2014 From: issues at jboss.org (Stephen Coy (JIRA)) Date: Wed, 18 Jun 2014 08:45:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-600) Improve Tomcat codebase - Managed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977356#comment-12977356 ] Stephen Coy commented on ARQ-600: --------------------------------- I noticed this while working on ARQ-866. Please assign this JIRA to me and I'll do the refactor > Improve Tomcat codebase - Managed > --------------------------------- > > Key: ARQ-600 > URL: https://issues.jboss.org/browse/ARQ-600 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > After the Tomcat Container code clean up, tomcat-common, it seems all the Managed Tomcat containers are identical both in impl and configuration. > We can create a similar tomcat-common-managed that will have the common parts between the different versions. > {note} > If Tomcat Managed 5.5, 6 and 7 are identical, why do we have 3 versions? > {note} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 12:25:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 18 Jun 2014 12:25:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-600) Improve Tomcat codebase - Managed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-600: ------------------------------ Assignee: Stephen Coy > Improve Tomcat codebase - Managed > --------------------------------- > > Key: ARQ-600 > URL: https://issues.jboss.org/browse/ARQ-600 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Aslak Knutsen > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.Final > > > After the Tomcat Container code clean up, tomcat-common, it seems all the Managed Tomcat containers are identical both in impl and configuration. > We can create a similar tomcat-common-managed that will have the common parts between the different versions. > {note} > If Tomcat Managed 5.5, 6 and 7 are identical, why do we have 3 versions? > {note} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 19 03:03:24 2014 From: issues at jboss.org (=?UTF-8?Q?jean-fran=C3=A7ois_Lefebvre_=28JIRA=29?=) Date: Thu, 19 Jun 2014 03:03:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1800) SQL scripts are loaded with the default charset In-Reply-To: References: Message-ID: jean-fran?ois Lefebvre created ARQ-1800: ------------------------------------------- Summary: SQL scripts are loaded with the default charset Key: ARQ-1800 URL: https://issues.jboss.org/browse/ARQ-1800 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Reporter: jean-fran?ois Lefebvre Assignee: Bartosz Majsak SQLSripts are loaded with the default plateform charset. Could you please add a property like this : XXX to set the default scripts encoding. see org.jboss.arquillian.persistence.script.ScriptLoader reader = new BufferedReader(new InputStreamReader(inputStream)); -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 19 03:43:25 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 19 Jun 2014 03:43:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1800) SQL scripts are loaded with the default charset In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1800: -------------------------------- Affects Version/s: persistence_1.0.0.Alpha7 > SQL scripts are loaded with the default charset > ----------------------------------------------- > > Key: ARQ-1800 > URL: https://issues.jboss.org/browse/ARQ-1800 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: jean-fran?ois Lefebvre > Assignee: Bartosz Majsak > > SQLSripts are loaded with the default plateform charset. > Could you please add a property like this : > > XXX > > to set the default scripts encoding. > see org.jboss.arquillian.persistence.script.ScriptLoader > reader = new BufferedReader(new InputStreamReader(inputStream)); -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 19 03:43:25 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 19 Jun 2014 03:43:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1800) SQL scripts are loaded with the default charset In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1800: -------------------------------- Fix Version/s: persistence_1.0.0.next > SQL scripts are loaded with the default charset > ----------------------------------------------- > > Key: ARQ-1800 > URL: https://issues.jboss.org/browse/ARQ-1800 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: jean-fran?ois Lefebvre > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > SQLSripts are loaded with the default plateform charset. > Could you please add a property like this : > > XXX > > to set the default scripts encoding. > see org.jboss.arquillian.persistence.script.ScriptLoader > reader = new BufferedReader(new InputStreamReader(inputStream)); -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 19 03:43:25 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 19 Jun 2014 03:43:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1800) SQL scripts are loaded with the default charset In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977601#comment-12977601 ] Bartosz Majsak commented on ARQ-1800: ------------------------------------- Thanks for the feature request. Of course this will be handy feature. Shall we consider UTF-8 as a default? Moreover would you be interested in contributing this improvement? That would be simply awesome. > SQL scripts are loaded with the default charset > ----------------------------------------------- > > Key: ARQ-1800 > URL: https://issues.jboss.org/browse/ARQ-1800 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: jean-fran?ois Lefebvre > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > SQLSripts are loaded with the default plateform charset. > Could you please add a property like this : > > XXX > > to set the default scripts encoding. > see org.jboss.arquillian.persistence.script.ScriptLoader > reader = new BufferedReader(new InputStreamReader(inputStream)); -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 19 06:34:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 19 Jun 2014 06:34:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-866) Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-866: ------------------------------ Fix Version/s: tomcat_1.0.0.Final > Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > ------------------------------------------------------------------------------------------------- > > Key: ARQ-866 > URL: https://issues.jboss.org/browse/ARQ-866 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR3 > Reporter: Dan Allen > Fix For: tomcat_1.0.0.Final > > > The Tomcat managed container adapter assumes that catalina.base is the same as catalina.home. > {code} > String absolutePath = new File(CATALINA_HOME).getAbsolutePath(); > ... > cmd.add("-Dcatalina.base=" + absolutePath); > cmd.add("-Dcatalina.home=" + absolutePath); > {code} > However, this is not necessary true. For instance, when using Tomcat from Eclipse, the catalina.base (which includes the configuration files) is managed inside the Eclipse workspace. This allows the developer to modify Tomcat settings without affecting the system installation. > The fix for this problem is to add a configuration property named "catalinaBase" and honor if it's set when building the startup script. > This affects all the Tomcat managed containers (5, 6 and 7). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 19 06:34:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 19 Jun 2014 06:34:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-866) Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-866: ------------------------------ Status: Resolved (was: Pull Request Sent) Assignee: Stephen Coy Resolution: Done pushed upstream; https://github.com/arquillian/arquillian-container-tomcat/commit/e60311545cf31dd1e33050d3a97ea1187a79bf1f > Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > ------------------------------------------------------------------------------------------------- > > Key: ARQ-866 > URL: https://issues.jboss.org/browse/ARQ-866 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR3 > Reporter: Dan Allen > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.Final > > > The Tomcat managed container adapter assumes that catalina.base is the same as catalina.home. > {code} > String absolutePath = new File(CATALINA_HOME).getAbsolutePath(); > ... > cmd.add("-Dcatalina.base=" + absolutePath); > cmd.add("-Dcatalina.home=" + absolutePath); > {code} > However, this is not necessary true. For instance, when using Tomcat from Eclipse, the catalina.base (which includes the configuration files) is managed inside the Eclipse workspace. This allows the developer to modify Tomcat settings without affecting the system installation. > The fix for this problem is to add a configuration property named "catalinaBase" and honor if it's set when building the startup script. > This affects all the Tomcat managed containers (5, 6 and 7). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 20 03:07:28 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Fri, 20 Jun 2014 03:07:28 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1801) @Before not called with arquillian-junit-standalone In-Reply-To: References: Message-ID: Thomas Diesler created ARQ-1801: ----------------------------------- Summary: @Before not called with arquillian-junit-standalone Key: ARQ-1801 URL: https://issues.jboss.org/browse/ARQ-1801 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler When using {code} org.jboss.arquillian.junit arquillian-junit-standalone 1.1.4.Final {code} @BeforeClass and @Before are not called. Using arquillian-junit-container they are. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 20 03:09:24 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Fri, 20 Jun 2014 03:09:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1801) @Before not called with arquillian-junit-standalone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated ARQ-1801: -------------------------------- Affects Version/s: 1.1.4.Final > @Before not called with arquillian-junit-standalone > --------------------------------------------------- > > Key: ARQ-1801 > URL: https://issues.jboss.org/browse/ARQ-1801 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Thomas Diesler > > When using > {code} > > org.jboss.arquillian.junit > arquillian-junit-standalone > 1.1.4.Final > > {code} > @BeforeClass and @Before are not called. > Using arquillian-junit-container they are. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 12:21:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 12:21:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1801) @Before not called with arquillian-junit-standalone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1801: ------------------------------- Fix Version/s: 1.1.5.Final > @Before not called with arquillian-junit-standalone > --------------------------------------------------- > > Key: ARQ-1801 > URL: https://issues.jboss.org/browse/ARQ-1801 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Thomas Diesler > Fix For: 1.1.5.Final > > > When using > {code} > > org.jboss.arquillian.junit > arquillian-junit-standalone > 1.1.4.Final > > {code} > @BeforeClass and @Before are not called. > Using arquillian-junit-container they are. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 12:55:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 12:55:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1792) allow deployment with default interfaces instead of static methods In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978327#comment-12978327 ] Aslak Knutsen commented on ARQ-1792: ------------------------------------ Nice idea, but to my knowledge, default interface methods still need an instance of the Object to call it. The reason it's currently static is because we're creating the Deployment before we have a Instance of the TestClass available. > allow deployment with default interfaces instead of static methods > ------------------------------------------------------------------ > > Key: ARQ-1792 > URL: https://issues.jboss.org/browse/ARQ-1792 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Caleb Cushing > > I'd like to be able to do an > {code:java} > @Deployment > default Archive createDeployment() { ... } > {code} > and then just apply the interface to my test class -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 12:57:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 12:57:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1791) add geronimo managed and/or remote adapters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978328#comment-12978328 ] Aslak Knutsen commented on ARQ-1791: ------------------------------------ If you have some experience with this Container, I'm happy to guide you in implement this. ? > add geronimo managed and/or remote adapters > ------------------------------------------- > > Key: ARQ-1791 > URL: https://issues.jboss.org/browse/ARQ-1791 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Peter Butkovic > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 12:57:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 12:57:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1789) add tomcat 8 managed and/or remote container adapters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978329#comment-12978329 ] Aslak Knutsen commented on ARQ-1789: ------------------------------------ Have you tried running the Managed/Remote 7 against a 8 Container? > add tomcat 8 managed and/or remote container adapters > ----------------------------------------------------- > > Key: ARQ-1789 > URL: https://issues.jboss.org/browse/ARQ-1789 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Peter Butkovic > > I'd like to see managed and/or remote support for tomcat 8 available in arquillian. > As I need to do some container pre-configuration/patching before the run as well as to have clear classpath separation. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 12:59:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 12:59:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1777) Test hangs on remote Tomcat 6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1777: ------------------------------- Component/s: Tomcat Containers > Test hangs on remote Tomcat 6 > ----------------------------- > > Key: ARQ-1777 > URL: https://issues.jboss.org/browse/ARQ-1777 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Pramod Kankure > > I have observed that test hangs when executing on tomcat 6 remote container. > My arquillian.xml looks like below. ( I don't use authentication for jmx) > > xmlns="http://jboss.org/schema/arquillian" > xsi:schemaLocation="http://jboss.org/schema/arquillian > http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> > > > > > 1776 > localhost > 8090 > > > > > The test do stops with an error when the server is down or wrong HTTP port is specified. It does execute @deployment method of the test but never comes to execute the test method annoted with [~test.todd] -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 13:03:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 13:03:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1777) Test hangs on remote Tomcat 6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978330#comment-12978330 ] Aslak Knutsen commented on ARQ-1777: ------------------------------------ Are you referring to this? https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-common/src/main/java/org/jboss/arquillian/container/tomcat/IOUtil.java#L136 > Test hangs on remote Tomcat 6 > ----------------------------- > > Key: ARQ-1777 > URL: https://issues.jboss.org/browse/ARQ-1777 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Pramod Kankure > > I have observed that test hangs when executing on tomcat 6 remote container. > My arquillian.xml looks like below. ( I don't use authentication for jmx) > > xmlns="http://jboss.org/schema/arquillian" > xsi:schemaLocation="http://jboss.org/schema/arquillian > http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> > > > > > 1776 > localhost > 8090 > > > > > The test do stops with an error when the server is down or wrong HTTP port is specified. It does execute @deployment method of the test but never comes to execute the test method annoted with [~test.todd] -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 13:03:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 13:03:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1772) Arquillian Debug does not print real event class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1772: ------------------------------- Fix Version/s: 1.1.5.Final > Arquillian Debug does not print real event class > ------------------------------------------------ > > Key: ARQ-1772 > URL: https://issues.jboss.org/browse/ARQ-1772 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Fix For: 1.1.5.Final > > > When using inheritance to define events, Arquillian Debug prints out following: > {code} > (E) PrepareDrone > (O) EventRegisterObserver.register > (O) DroneConfigurator.prepareDrone > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) Before > (O) EventRegisterObserver.register > (O) DroneLifecycleManager.before > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > {code} > Which is not really super useful, as debug log can't show what actual events were fired. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 13:03:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 13:03:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1773: ------------------------------- Fix Version/s: 1.1.5.Final > JUnittests pass when exception is thrown from @Before-annotated method > ---------------------------------------------------------------------- > > Key: ARQ-1773 > URL: https://issues.jboss.org/browse/ARQ-1773 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Mattias Persson > Fix For: 1.1.5.Final > > Attachments: arquillian_test_should_fail.zip > > > When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 13:07:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 13:07:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1768) Rare fail of org.jboss.as.arquillian.testng.BasicTestNGIntegrationTestCase due to NPE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978332#comment-12978332 ] Aslak Knutsen commented on ARQ-1768: ------------------------------------ This one was found to be a problem with the 'client lib v of eap' that rhq matrix depended on directly I believe? [~pilhuhn]? > Rare fail of org.jboss.as.arquillian.testng.BasicTestNGIntegrationTestCase due to NPE > ------------------------------------------------------------------------------------- > > Key: ARQ-1768 > URL: https://issues.jboss.org/browse/ARQ-1768 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Final > Reporter: Pavel Jelinek > > See: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-RHEL-matrix-OracleJDK6/156/jdk=java16_default,label_exp=RHEL5%26%26x86_64/testReport/org.jboss.as.arquillian.testng/BasicTestNGIntegrationTestCase/arquillianBeforeSuite/ > Stacktrace > org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:183) > at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:111) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:198) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68) > at org.jboss.arquillian.testng.Arquillian.arquillianBeforeSuite(Arquillian.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:277) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) > at org.testng.TestNG.run(TestNG.java:999) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:70) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:111) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [60] s > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:179) > ... 83 more > Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [60] s > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:179) > ... 83 more > Standard Output > 14:39:13,044 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1 > 14:39:13,333 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1 > 14:39:13,473 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.3.0.Beta1 (AS 7.4.0.Final-redhat-SNAPSHOT) starting > 14:39:14,312 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > at org.jboss.as.server.ServerService.boot(ServerService.java:321) [jboss-as-server-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:253) [jboss-as-controller-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: javax.xml.stream.XMLStreamException: JBAS014674: Failed to load module org.jboss.as.security > at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:154) [jboss-as-controller-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:435) [jboss-as-server-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [jboss-as-server-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [jboss-as-server-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2] > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2] > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > ... 3 more > Caused by: java.util.concurrent.ExecutionException: java.lang.NullPointerException > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) [rt.jar:1.6.0_45] > at java.util.concurrent.FutureTask.get(FutureTask.java:83) [rt.jar:1.6.0_45] > at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:146) [jboss-as-controller-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > ... 9 more > Caused by: java.lang.NullPointerException > at sun.net.www.protocol.jar.JarURLConnection.getUseCaches(JarURLConnection.java:309) [rt.jar:1.6.0_45] > at sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream.close(JarURLConnection.java:92) [rt.jar:1.6.0_45] > at sun.nio.cs.StreamDecoder.implClose(StreamDecoder.java:358) [rt.jar:1.6.0_45] > at sun.nio.cs.StreamDecoder.close(StreamDecoder.java:173) [rt.jar:1.6.0_45] > at java.io.InputStreamReader.close(InputStreamReader.java:182) [rt.jar:1.6.0_45] > at java.io.BufferedReader.close(BufferedReader.java:497) [rt.jar:1.6.0_45] > at java.util.ServiceLoader.parse(ServiceLoader.java:287) [rt.jar:1.6.0_45] > at java.util.ServiceLoader.access$200(ServiceLoader.java:164) [rt.jar:1.6.0_45] > at java.util.ServiceLoader$LazyIterator.hasNext(ServiceLoader.java:332) [rt.jar:1.6.0_45] > at java.util.ServiceLoader$1.hasNext(ServiceLoader.java:422) [rt.jar:1.6.0_45] > at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:179) [jboss-as-controller-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.parsing.ExtensionXml.access$000(ExtensionXml.java:68) [jboss-as-controller-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:126) [jboss-as-controller-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:123) [jboss-as-controller-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_45] > at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1] > 14:39:14,327 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > 14:39:14,351 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015950: JBoss EAP 6.3.0.Beta1 (AS 7.4.0.Final-redhat-SNAPSHOT) stopped in 11ms >  -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 13:09:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 13:09:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1742) Exception thrown before BeforeSuite event are not reported to user. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1742: ------------------------------- Fix Version/s: 1.1.5.Final > Exception thrown before BeforeSuite event are not reported to user. > ------------------------------------------------------------------- > > Key: ARQ-1742 > URL: https://issues.jboss.org/browse/ARQ-1742 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Fix For: 1.1.5.Final > > > *When*: > My extensions observes ManagerStarted event and something gets wrong and an exception is thrown. > *Then*: > Arquillian (Or rather JUnit) silently ignores the exception, causing subsequent children runs to be ignored: > https://github.com/arquillian/arquillian-core/blob/master/junit/core/src/main/java/org/jboss/arquillian/junit/Arquillian.java#L95 > This behavior should be improved. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 13:11:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 13:11:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1741) Injector might throw unchecked TypeNotPresentException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978333#comment-12978333 ] Aslak Knutsen commented on ARQ-1741: ------------------------------------ You mean the inject method should declare the RuntimeException TypeNotPresentException ? > Injector might throw unchecked TypeNotPresentException > ------------------------------------------------------ > > Key: ARQ-1741 > URL: https://issues.jboss.org/browse/ARQ-1741 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Priority: Minor > > *When*: > I call Injector.get().inject() > *And*: > Service to be injected is not on classpath > *Then*: > Arquillian throws TypeNotPresentException. This is fine, however it should be in API so when looking into code this is more obvious. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 13:13:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 13:13:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1717) Update Arquillian BOM to use ShrinkWrap Resolver 2.1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1717. ------------------------------ Assignee: Aslak Knutsen Fix Version/s: 1.1.4.Final Resolution: Out of Date Was done for 1.1.4, missed this issue. > Update Arquillian BOM to use ShrinkWrap Resolver 2.1.0 > ------------------------------------------------------ > > Key: ARQ-1717 > URL: https://issues.jboss.org/browse/ARQ-1717 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Karel Piwko > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > Update SWR to 2.1.0. This brings support for Maven 3.1.0 and newer. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 13:15:29 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 13:15:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1684) Jacoco extension filters do not work as advertised In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1684: ------------------------------- Fix Version/s: jacoco_1.0.0.next > Jacoco extension filters do not work as advertised > -------------------------------------------------- > > Key: ARQ-1684 > URL: https://issues.jboss.org/browse/ARQ-1684 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha6 > Reporter: Rich DiCroce > Fix For: jacoco_1.0.0.next > > > The Jacoco includes/excludes mechanism does not work the way the [1.0.0.Alpha5 release announcement|http://arquillian.org/blog/2012/11/27/arquillian-extension-jacoco-1-0-0-Alpha5/] implies it does. Specifically, the release announcement shows excluding a package and then including some sub-packages. This implies that includes have precedence over excludes, but that is not true. It's clear from looking at the source code that includes and excludes just get turned into filters that are all ANDed together. So if you have > exclude some.package.* > include some.package.foo.* > then some.package.foo will not be included because the exclude for some.package will return false. Effectively, excludes have priority over includes. > This would be fine if not for the fact that an "include everything" filter is automatically added. This, combined with exclusions having priority, breaks a key use case, namely: I want to exclude all packages that are not my own code. I can't just > include my.package.* > because of the automatic include all filter, and I can't > exclude * > include my.package.* > because the exclude blocks out the include. > Including everything is a problem because then so many classes have to be instrumented that the test just hangs and the archive never gets deployed. For me, this makes the Jacoco extension completely unusable. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 13:49:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 13:49:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1607) Please avoid using arquillian.launch files, it makes Eclipse generate error logs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1607: ------------------------------- Fix Version/s: 1.1.5.Final > Please avoid using arquillian.launch files, it makes Eclipse generate error logs > -------------------------------------------------------------------------------- > > Key: ARQ-1607 > URL: https://issues.jboss.org/browse/ARQ-1607 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: Eclipse > Reporter: Fred Bricon > Priority: Minor > Fix For: 1.1.5.Final > > > When imported in Eclipse, projects containing arquillian.launch files make Eclipse barf as it expects a valid Eclipse Launch configuration xml file. > It's just an error in the .metadata/.log, but the sight of such ugly stacktraces could be frightening/annoying for some > {noformat} > !MESSAGE org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Contenu non autoris? dans le prologue. occurred while reading launch configuration file: D:\tmp\arquillian-examples\arquillian-persistence-tutorial\target\test-classes\arquillian.launch. > !STACK 0 > org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Contenu non autoris? dans le prologue. > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198) > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441) > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368) > at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1388) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:998) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:489) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) > at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) > at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:237) > at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:300) > at org.eclipse.debug.internal.core.LaunchManager.createInfoFromXML(LaunchManager.java:929) > at org.eclipse.debug.internal.core.LaunchManager.getInfo(LaunchManager.java:1353) > at org.eclipse.debug.internal.core.LaunchConfiguration.getInfo(LaunchConfiguration.java:453) > at org.eclipse.debug.internal.core.LaunchConfiguration.getType(LaunchConfiguration.java:617) > at org.eclipse.debug.internal.core.LaunchManager.isValid(LaunchManager.java:2081) > at org.eclipse.debug.internal.core.LaunchManager.launchConfigurationAdded(LaunchManager.java:2104) > at org.eclipse.debug.internal.core.LaunchManager$LaunchManagerVisitor.visit(LaunchManager.java:382) > {noformat} > From IRC > {quote} > (15:46:37) fbricon: hey aslak, I'm looking at a some maven projects containing some arquillian.launch files > (15:47:18) fbricon: eclipse treats these as Launch configuration files and complains they're malformed xml > (15:47:38) fbricon: do the files need to be .launch? > 15:47:58) aslak: fbricon hehe yea.. noticed that as well.. > (15:48:22) aslak: it ended up being called arquillian.launch because that's the name of the -D property that does the same > (15:48:50) aslak: fbricon could you file an issue on this.. I'll add support for arquillian.launch.properties or arquillian-launch or similar > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 13:51:23 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 13:51:23 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1606) Support deploymentExportPath to export Exploded In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1606: ------------------------------- Fix Version/s: 1.1.5.Final > Support deploymentExportPath to export Exploded > ----------------------------------------------- > > Key: ARQ-1606 > URL: https://issues.jboss.org/browse/ARQ-1606 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.2.Final > Reporter: Aslak Knutsen > Fix For: 1.1.5.Final > > > Currently deploymentExportPath will export a Zipped file, but the reason for exporting it is to see the content. Allow to export as exploded. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 13:57:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 13:57:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1443) @ArquillianResource ManagementClient doesn't work (AS 7) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978339#comment-12978339 ] Aslak Knutsen commented on ARQ-1443: ------------------------------------ Correct. :) > @ArquillianResource ManagementClient doesn't work (AS 7) > -------------------------------------------------------- > > Key: ARQ-1443 > URL: https://issues.jboss.org/browse/ARQ-1443 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JBoss AS Containers > Affects Versions: 1.0.4.Final > Reporter: Ondrej Zizka > > {code} > @RunWith( Arquillian.class ) > public class ExtActionsMigrationTest extends ExternalMigratorsTestEnv { > @ArquillianResource private ManagementClient mc; > @Test > public void testCliAction() throws Exception { > TestUtils.printTestBanner(); > doTest( "CliActionTest", null, DirPreparation.NOOP ); > {code} > Exception: > {code} > Caused by: java.lang.RuntimeException: Provider for type class org.jboss.as.arquillian.container.ManagementClient returned a null value: org.jboss.as.arquillian.container.ManagementClientProvider at 72bd402d > at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.lookup(ArquillianResourceTestEnricher.java:115) > at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.enrich(ArquillianResourceTestEnricher.java:57) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > ... > {code} > I'm using: > {code} > > org.jboss.arquillian.junit > arquillian-junit-container > test > > > org.jboss.as > jboss-as-arquillian-container-managed > ${arq.asContainer.version} > test > jbosgi-spi org.jboss.osgi.spi > > {code} > JBoss EAP comes from org.jboss.as:jboss-as-dist:${as.download.version}:zip > Whole container config is below. > {code} > > > ${basedir}/target/as-dist > > -Djboss.inst=${basedir}/target/jboss-as-7.1.1.Final > ${jboss.server.config.file.name:standalone.xml} > true > ${node0:127.0.0.1} > ${as.managementPort:9999} > > ${as.debug.port:8787} ${as.managementPort:9999} > 8 > > > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 14:01:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 14:01:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1437) NPE in ExceptionProxy.readExternal() for root cause leads to deserializationProblem = true In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1437: ------------------------------- Fix Version/s: 1.1.5.Final > NPE in ExceptionProxy.readExternal() for root cause leads to deserializationProblem = true > ------------------------------------------------------------------------------------------ > > Key: ARQ-1437 > URL: https://issues.jboss.org/browse/ARQ-1437 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.2.Final, 1.1.0.Final > Reporter: Falko M. > Priority: Minor > Fix For: 1.1.5.Final > > > See line 199 (for 1.0.2.Final): > {code} > // reset the cause, so we can de-serialize them individual > SecurityActions.setFieldValue(Throwable.class, original, "cause", causeProxy.createException()); > {code} > For the root cause of an exception, {{causeProxy}} will always be {{null}} and so a {{NullPointerException}} is thrown. > As the code is wrapped in a try block with follwoing catch block: > {code} > catch (Throwable e) // ClassNotFoundExcpetion / NoClassDefFoundError > { > // ignore, could not load class on client side, move on and create a fake 'proxy' later > deserializationProblem = true; > } > {code} > the NPE is caught and is "expected" to be a {{ClassNotFoundExcpetion}} or {{NoClassDefFoundError}} which is clearly not the case. > *Possible fix:* > {{original.cause}} should only be overwritten when {{causeProxy}} is *not* null. > *More context information:* > I came across this problem while trying to find the reason for an unexpected {{ArquillianProxyException}}: > {code}org.jboss.arquillian.test.spi.ArquillianProxyException: javax.ejb.EJBException : javax.persistence.OptimisticLockException [Proxied because : Original exception not deserilizable, ClassNotFoundException]{code} > The root problem was not the NPE, but the {{ClassNotFoundException}} mislead me and so I debugged {{ExceptionProxy}}. > I my case there is an {{InvalidClassException}} because of an older hibernate version on the client side. > +So that is another problem of {{ExceptionProxy}} as it assumes that only {{ClassNotFoundExcpetion}} or {{NoClassDefFoundError}} can occur!+ -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 14:13:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 14:13:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-286) Should support JUnit @Rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-286: ------------------------------ Fix Version/s: 1.1.5.Final (was: 2.0.0.CR1) > Should support JUnit @Rules > --------------------------- > > Key: ARQ-286 > URL: https://issues.jboss.org/browse/ARQ-286 > Project: Arquillian > Issue Type: Feature Request > Components: Test Harness Integration > Reporter: Aslak Knutsen > Fix For: 1.1.5.Final > > > Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. > It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 14:13:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 14:13:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-181) When using @Test expected exception, the internal state of the TestResult is unknown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-181: ------------------------------ Fix Version/s: 1.1.5.Final > When using @Test expected exception, the internal state of the TestResult is unknown > ------------------------------------------------------------------------------------ > > Key: ARQ-181 > URL: https://issues.jboss.org/browse/ARQ-181 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > JUnit > @Test(expected=Exception.class) > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG and JUnit to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 15:45:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 15:45:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1801) @Before not called with arquillian-junit-standalone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen reassigned ARQ-1801: ---------------------------------- Assignee: Aslak Knutsen > @Before not called with arquillian-junit-standalone > --------------------------------------------------- > > Key: ARQ-1801 > URL: https://issues.jboss.org/browse/ARQ-1801 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > When using > {code} > > org.jboss.arquillian.junit > arquillian-junit-standalone > 1.1.4.Final > > {code} > @BeforeClass and @Before are not called. > Using arquillian-junit-container they are. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 15:45:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 15:45:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1801) @Before not called with arquillian-junit-standalone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1801. -------------------------------- Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/d55ac3ca902b1ba91e4992ce58febbb288fdea9a > @Before not called with arquillian-junit-standalone > --------------------------------------------------- > > Key: ARQ-1801 > URL: https://issues.jboss.org/browse/ARQ-1801 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > When using > {code} > > org.jboss.arquillian.junit > arquillian-junit-standalone > 1.1.4.Final > > {code} > @BeforeClass and @Before are not called. > Using arquillian-junit-container they are. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 16:09:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 16:09:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1772) Arquillian Debug does not print real event class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1772. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/a4d24f23d98369e0b548e0427404119b720b3de3 > Arquillian Debug does not print real event class > ------------------------------------------------ > > Key: ARQ-1772 > URL: https://issues.jboss.org/browse/ARQ-1772 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > When using inheritance to define events, Arquillian Debug prints out following: > {code} > (E) PrepareDrone > (O) EventRegisterObserver.register > (O) DroneConfigurator.prepareDrone > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) Before > (O) EventRegisterObserver.register > (O) DroneLifecycleManager.before > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > {code} > Which is not really super useful, as debug log can't show what actual events were fired. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 17:47:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 17:47:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1742) Exception thrown before BeforeSuite event are not reported to user. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1742. -------------------------------- Assignee: Aslak Knutsen Resolution: Done It seemed to me the failure happened in Junit either it was during boot or during beforeSuite, either way.. But couldn't hurt to handle the boot exceptions in the same way as beforeSuite. pushed upstream, https://github.com/arquillian/arquillian-core/commit/e43f9e99639874ab4bbe01cfceb157bbded84611 > Exception thrown before BeforeSuite event are not reported to user. > ------------------------------------------------------------------- > > Key: ARQ-1742 > URL: https://issues.jboss.org/browse/ARQ-1742 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > *When*: > My extensions observes ManagerStarted event and something gets wrong and an exception is thrown. > *Then*: > Arquillian (Or rather JUnit) silently ignores the exception, causing subsequent children runs to be ignored: > https://github.com/arquillian/arquillian-core/blob/master/junit/core/src/main/java/org/jboss/arquillian/junit/Arquillian.java#L95 > This behavior should be improved. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 21 18:23:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sat, 21 Jun 2014 18:23:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1606) Support deploymentExportPath to export Exploded In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1606. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/20507a7d0fce3b52a014842a3b33e8b67bef5797 > Support deploymentExportPath to export Exploded > ----------------------------------------------- > > Key: ARQ-1606 > URL: https://issues.jboss.org/browse/ARQ-1606 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.2.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Currently deploymentExportPath will export a Zipped file, but the reason for exporting it is to see the content. Allow to export as exploded. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 08:44:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 22 Jun 2014 08:44:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978383#comment-12978383 ] Stefan Miklosovic commented on ARQ-1728: ---------------------------------------- [~lfryc] it should be sufficient just to read server log file in a separate thread which would mimic the behaviour of file tailing, everything which would be written to some kind of buffer while test execution in logically inside a test method would be related to that particular test method and fired from logging extension as a reporting event > Add possibility to report AS console output related to test methods > ------------------------------------------------------------------- > > Key: ARQ-1728 > URL: https://issues.jboss.org/browse/ARQ-1728 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > > There is not any possiblity to see what AS has written out to console with test methods. > Investigate a way how to match output from AS with particular test method during which that console output has occured. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 08:48:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 22 Jun 2014 08:48:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978383#comment-12978383 ] Stefan Miklosovic edited comment on ARQ-1728 at 6/22/14 8:48 AM: ----------------------------------------------------------------- [~lfryc] it should be sufficient just to read server log file in a separate thread which would mimic the behaviour of file tailing, everything which would be written to some kind of buffer while test execution in logically inside a test method would be related to that particular test method and fired from logging extension as a reporting event However I can not image how this would be implemented with remote containers (+ they can be located at different physical machine). The better solution seems to be using some kind of management console of container as such (e.g. jboss-cli.sh) but that console has only ability to read logs "once", so no tailing. Since every log is in the end written out to some file, the original solution seems to be universal. However, only the fly modification of logs (e.g. filtering them) would be little bit tricky. There can be custom Spacelift task written particulary for this whole JIRA issue. was (Author: smikloso): [~lfryc] it should be sufficient just to read server log file in a separate thread which would mimic the behaviour of file tailing, everything which would be written to some kind of buffer while test execution in logically inside a test method would be related to that particular test method and fired from logging extension as a reporting event > Add possibility to report AS console output related to test methods > ------------------------------------------------------------------- > > Key: ARQ-1728 > URL: https://issues.jboss.org/browse/ARQ-1728 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > > There is not any possiblity to see what AS has written out to console with test methods. > Investigate a way how to match output from AS with particular test method during which that console output has occured. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 10:49:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 10:49:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1802) Expose the underlying HTTPConnection used by Servlet protocol to allow new protocols manipulation access. In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1802: ---------------------------------- Summary: Expose the underlying HTTPConnection used by Servlet protocol to allow new protocols manipulation access. Key: ARQ-1802 URL: https://issues.jboss.org/browse/ARQ-1802 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Test Protocol SPIs and Implementation Affects Versions: 1.1.4.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.1.5.Final -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 10:51:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 10:51:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1802) Expose the underlying HTTPConnection used by Servlet protocol to allow new protocols manipulation access. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1802: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/66 > Expose the underlying HTTPConnection used by Servlet protocol to allow new protocols manipulation access. > --------------------------------------------------------------------------------------------------------- > > Key: ARQ-1802 > URL: https://issues.jboss.org/browse/ARQ-1802 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.4.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 10:55:23 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 10:55:23 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1802) Expose the underlying HTTPConnection used by Servlet protocol to allow new protocols manipulation access. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1802: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/af684bb18f44d8300afa1cf8b758d1f237ec5a8d > Expose the underlying HTTPConnection used by Servlet protocol to allow new protocols manipulation access. > --------------------------------------------------------------------------------------------------------- > > Key: ARQ-1802 > URL: https://issues.jboss.org/browse/ARQ-1802 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.4.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 12:17:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 12:17:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1437) NPE in ExceptionProxy.readExternal() for root cause leads to deserializationProblem = true In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1437. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/92987573ff8fb419e6996b54ae7ab4db56ba8797 > NPE in ExceptionProxy.readExternal() for root cause leads to deserializationProblem = true > ------------------------------------------------------------------------------------------ > > Key: ARQ-1437 > URL: https://issues.jboss.org/browse/ARQ-1437 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.2.Final, 1.1.0.Final > Reporter: Falko M. > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > See line 199 (for 1.0.2.Final): > {code} > // reset the cause, so we can de-serialize them individual > SecurityActions.setFieldValue(Throwable.class, original, "cause", causeProxy.createException()); > {code} > For the root cause of an exception, {{causeProxy}} will always be {{null}} and so a {{NullPointerException}} is thrown. > As the code is wrapped in a try block with follwoing catch block: > {code} > catch (Throwable e) // ClassNotFoundExcpetion / NoClassDefFoundError > { > // ignore, could not load class on client side, move on and create a fake 'proxy' later > deserializationProblem = true; > } > {code} > the NPE is caught and is "expected" to be a {{ClassNotFoundExcpetion}} or {{NoClassDefFoundError}} which is clearly not the case. > *Possible fix:* > {{original.cause}} should only be overwritten when {{causeProxy}} is *not* null. > *More context information:* > I came across this problem while trying to find the reason for an unexpected {{ArquillianProxyException}}: > {code}org.jboss.arquillian.test.spi.ArquillianProxyException: javax.ejb.EJBException : javax.persistence.OptimisticLockException [Proxied because : Original exception not deserilizable, ClassNotFoundException]{code} > The root problem was not the NPE, but the {{ClassNotFoundException}} mislead me and so I debugged {{ExceptionProxy}}. > I my case there is an {{InvalidClassException}} because of an older hibernate version on the client side. > +So that is another problem of {{ExceptionProxy}} as it assumes that only {{ClassNotFoundExcpetion}} or {{NoClassDefFoundError}} can occur!+ -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 14:25:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 14:25:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1576) RuntimeException after testng suite switched In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978403#comment-12978403 ] Aslak Knutsen commented on ARQ-1576: ------------------------------------ The createSuiteContext calls happen on all Test lifecycle events, and is not wrong. Updating the given example to use Graphene 2.0.3.Final which rely on Drone 1.3.0.Final work. > RuntimeException after testng suite switched > -------------------------------------------- > > Key: ARQ-1576 > URL: https://issues.jboss.org/browse/ARQ-1576 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.2.Final > Reporter: Ji?? ?tefek > Attachments: reproducer.zip > > > Having a suite consisting of two suites. > After first suite finishes, then I get this: > {code} > arquillianBeforeTest(org.arquillian.example.Test2) Time elapsed: 6.373 sec <<< FAILURE! > java.lang.RuntimeException > at org.jboss.arquillian.drone.impl.DroneInstanceCreator.createDroneInstance(DroneInstanceCreator.java:96) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.getDroneInstance(DroneTestEnricher.java:111) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:72) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:653) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1220) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177) > at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:124) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:41) > at org.jboss.arquillian.drone.impl.DroneCallableCreator$1.call(DroneCallableCreator.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:124) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:41) > at org.jboss.arquillian.drone.impl.DroneCallableCreator$1.call(DroneCallableCreator.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > {code} > and this: > {code} > arquillianAfterClass(org.arquillian.example.Test2) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterClass(Arquillian.java:122) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138) > at org.testng.internal.TestMethodWorker.invokeAfterClassMethods(TestMethodWorker.java:225) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:114) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1220) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177) > at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 14:25:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 14:25:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1576) RuntimeException after testng suite switched In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen reassigned ARQ-1576: ---------------------------------- Assignee: Aslak Knutsen > RuntimeException after testng suite switched > -------------------------------------------- > > Key: ARQ-1576 > URL: https://issues.jboss.org/browse/ARQ-1576 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.2.Final > Reporter: Ji?? ?tefek > Assignee: Aslak Knutsen > Attachments: reproducer.zip > > > Having a suite consisting of two suites. > After first suite finishes, then I get this: > {code} > arquillianBeforeTest(org.arquillian.example.Test2) Time elapsed: 6.373 sec <<< FAILURE! > java.lang.RuntimeException > at org.jboss.arquillian.drone.impl.DroneInstanceCreator.createDroneInstance(DroneInstanceCreator.java:96) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.getDroneInstance(DroneTestEnricher.java:111) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:72) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:653) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1220) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177) > at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:124) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:41) > at org.jboss.arquillian.drone.impl.DroneCallableCreator$1.call(DroneCallableCreator.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:124) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:41) > at org.jboss.arquillian.drone.impl.DroneCallableCreator$1.call(DroneCallableCreator.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > {code} > and this: > {code} > arquillianAfterClass(org.arquillian.example.Test2) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterClass(Arquillian.java:122) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138) > at org.testng.internal.TestMethodWorker.invokeAfterClassMethods(TestMethodWorker.java:225) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:114) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1220) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177) > at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 14:27:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 14:27:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1576) RuntimeException after testng suite switched In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1576: ------------------------------- Component/s: Extension - Drone (was: Test Protocol SPIs and Implementation) > RuntimeException after testng suite switched > -------------------------------------------- > > Key: ARQ-1576 > URL: https://issues.jboss.org/browse/ARQ-1576 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: 1.1.2.Final > Reporter: Ji?? ?tefek > Assignee: Aslak Knutsen > Attachments: reproducer.zip > > > Having a suite consisting of two suites. > After first suite finishes, then I get this: > {code} > arquillianBeforeTest(org.arquillian.example.Test2) Time elapsed: 6.373 sec <<< FAILURE! > java.lang.RuntimeException > at org.jboss.arquillian.drone.impl.DroneInstanceCreator.createDroneInstance(DroneInstanceCreator.java:96) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.getDroneInstance(DroneTestEnricher.java:111) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:72) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:653) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1220) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177) > at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:124) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:41) > at org.jboss.arquillian.drone.impl.DroneCallableCreator$1.call(DroneCallableCreator.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:124) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:41) > at org.jboss.arquillian.drone.impl.DroneCallableCreator$1.call(DroneCallableCreator.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > {code} > and this: > {code} > arquillianAfterClass(org.arquillian.example.Test2) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterClass(Arquillian.java:122) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138) > at org.testng.internal.TestMethodWorker.invokeAfterClassMethods(TestMethodWorker.java:225) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:114) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1220) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177) > at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 14:27:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 14:27:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1576) RuntimeException after testng suite switched In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1576: ------------------------------- Fix Version/s: drone_1.3.0.Final > RuntimeException after testng suite switched > -------------------------------------------- > > Key: ARQ-1576 > URL: https://issues.jboss.org/browse/ARQ-1576 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: 1.1.2.Final > Reporter: Ji?? ?tefek > Assignee: Aslak Knutsen > Fix For: drone_1.3.0.Final > > Attachments: reproducer.zip > > > Having a suite consisting of two suites. > After first suite finishes, then I get this: > {code} > arquillianBeforeTest(org.arquillian.example.Test2) Time elapsed: 6.373 sec <<< FAILURE! > java.lang.RuntimeException > at org.jboss.arquillian.drone.impl.DroneInstanceCreator.createDroneInstance(DroneInstanceCreator.java:96) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.getDroneInstance(DroneTestEnricher.java:111) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:72) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:653) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1220) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177) > at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:124) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:41) > at org.jboss.arquillian.drone.impl.DroneCallableCreator$1.call(DroneCallableCreator.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:124) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:41) > at org.jboss.arquillian.drone.impl.DroneCallableCreator$1.call(DroneCallableCreator.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > {code} > and this: > {code} > arquillianAfterClass(org.arquillian.example.Test2) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterClass(Arquillian.java:122) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138) > at org.testng.internal.TestMethodWorker.invokeAfterClassMethods(TestMethodWorker.java:225) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:114) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1220) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177) > at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 14:27:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 14:27:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1576) RuntimeException after testng suite switched In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1576. ------------------------------ Resolution: Out of Date > RuntimeException after testng suite switched > -------------------------------------------- > > Key: ARQ-1576 > URL: https://issues.jboss.org/browse/ARQ-1576 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: 1.1.2.Final > Reporter: Ji?? ?tefek > Assignee: Aslak Knutsen > Fix For: drone_1.3.0.Final > > Attachments: reproducer.zip > > > Having a suite consisting of two suites. > After first suite finishes, then I get this: > {code} > arquillianBeforeTest(org.arquillian.example.Test2) Time elapsed: 6.373 sec <<< FAILURE! > java.lang.RuntimeException > at org.jboss.arquillian.drone.impl.DroneInstanceCreator.createDroneInstance(DroneInstanceCreator.java:96) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.getDroneInstance(DroneTestEnricher.java:111) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:72) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:653) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1220) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177) > at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:124) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:41) > at org.jboss.arquillian.drone.impl.DroneCallableCreator$1.call(DroneCallableCreator.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:124) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:41) > at org.jboss.arquillian.drone.impl.DroneCallableCreator$1.call(DroneCallableCreator.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > {code} > and this: > {code} > arquillianAfterClass(org.arquillian.example.Test2) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterClass(Arquillian.java:122) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138) > at org.testng.internal.TestMethodWorker.invokeAfterClassMethods(TestMethodWorker.java:225) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:114) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1220) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177) > at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 17:55:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 17:55:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-286) Should support JUnit @Rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-286. ------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537dffe9721b97b267f259d1 > Should support JUnit @Rules > --------------------------- > > Key: ARQ-286 > URL: https://issues.jboss.org/browse/ARQ-286 > Project: Arquillian > Issue Type: Feature Request > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. > It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 17:55:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 17:55:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1758) Test passes although it fails unexpectedly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1758. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537dffe9721b97b267f259d1 > Test passes although it fails unexpectedly > ------------------------------------------ > > Key: ARQ-1758 > URL: https://issues.jboss.org/browse/ARQ-1758 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Robert Panzer > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > Attachments: debug.png > > > I have an erronous test class that cannot be loaded in the container due to a NoClassDefFoundError. (A dependent class is missing.) > The test passes unexpectedly and all test methods are reported to have passed although log entries or SystemOuts show that the methods are actually never invoked. > The problem seems to be a regression that came with the last release. > In JUnitTestRunner the TestResults exception is overwritten with null in such a case. > I will attach a screenshot of the debugger showing that. > I also have a try of a patch that I will link as soon as I prepared the pull request on github. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 17:55:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 17:55:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1796) Regression: JUnit ExpectedException is not handled correctly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1796. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537dffe9721b97b267f259d1 > Regression: JUnit ExpectedException is not handled correctly > ------------------------------------------------------------ > > Key: ARQ-1796 > URL: https://issues.jboss.org/browse/ARQ-1796 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Rich DiCroce > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > I have many tests using JUnit's ExcpectedException rule. In Arquillian 1.1.3, these tests worked perfectly. When I tried to update to 1.1.4, they broke. It seems like Arquillian now catches the exceptions before ExpectedException does, and propagates them back to the client. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 18:01:28 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 18:01:28 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1773. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/e39433696861f11588180894378c32f795da8085 > JUnittests pass when exception is thrown from @Before-annotated method > ---------------------------------------------------------------------- > > Key: ARQ-1773 > URL: https://issues.jboss.org/browse/ARQ-1773 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Mattias Persson > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > Attachments: arquillian_test_should_fail.zip > > > When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 18:01:29 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 18:01:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-286) Should support JUnit @Rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978405#comment-12978405 ] Aslak Knutsen edited comment on ARQ-286 at 6/22/14 6:00 PM: ------------------------------------------------------------ pushed upstream https://github.com/arquillian/arquillian-core/commit/e39433696861f11588180894378c32f795da8085 was (Author: aslak): pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537dffe9721b97b267f259d1 > Should support JUnit @Rules > --------------------------- > > Key: ARQ-286 > URL: https://issues.jboss.org/browse/ARQ-286 > Project: Arquillian > Issue Type: Feature Request > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. > It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 18:01:30 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 18:01:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1758) Test passes although it fails unexpectedly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978406#comment-12978406 ] Aslak Knutsen edited comment on ARQ-1758 at 6/22/14 6:00 PM: ------------------------------------------------------------- pushed upstream https://github.com/arquillian/arquillian-core/commit/e39433696861f11588180894378c32f795da8085 was (Author: aslak): pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537dffe9721b97b267f259d1 > Test passes although it fails unexpectedly > ------------------------------------------ > > Key: ARQ-1758 > URL: https://issues.jboss.org/browse/ARQ-1758 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Robert Panzer > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > Attachments: debug.png > > > I have an erronous test class that cannot be loaded in the container due to a NoClassDefFoundError. (A dependent class is missing.) > The test passes unexpectedly and all test methods are reported to have passed although log entries or SystemOuts show that the methods are actually never invoked. > The problem seems to be a regression that came with the last release. > In JUnitTestRunner the TestResults exception is overwritten with null in such a case. > I will attach a screenshot of the debugger showing that. > I also have a try of a patch that I will link as soon as I prepared the pull request on github. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 18:01:30 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 18:01:30 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1796) Regression: JUnit ExpectedException is not handled correctly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978407#comment-12978407 ] Aslak Knutsen edited comment on ARQ-1796 at 6/22/14 6:00 PM: ------------------------------------------------------------- pushed upstream https://github.com/arquillian/arquillian-core/commit/e39433696861f11588180894378c32f795da8085 was (Author: aslak): pushed upstream https://github.com/arquillian/arquillian-core/commit/b4d611c263bc0207537dffe9721b97b267f259d1 > Regression: JUnit ExpectedException is not handled correctly > ------------------------------------------------------------ > > Key: ARQ-1796 > URL: https://issues.jboss.org/browse/ARQ-1796 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Rich DiCroce > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > I have many tests using JUnit's ExcpectedException rule. In Arquillian 1.1.3, these tests worked perfectly. When I tried to update to 1.1.4, they broke. It seems like Arquillian now catches the exceptions before ExpectedException does, and propagates them back to the client. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 18:15:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 18:15:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1803) Deployments not being un-deploying when JUnit Category is used In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1803: ---------------------------------- Summary: Deployments not being un-deploying when JUnit Category is used Key: ARQ-1803 URL: https://issues.jboss.org/browse/ARQ-1803 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Harness Integration Affects Versions: 1.1.4.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.1.5.Final -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 18:26:23 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 18:26:23 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1803) Deployments not being un-deploying when JUnit Category is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1803: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/67 > Deployments not being un-deploying when JUnit Category is used > --------------------------------------------------------------- > > Key: ARQ-1803 > URL: https://issues.jboss.org/browse/ARQ-1803 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Harness Integration > Affects Versions: 1.1.4.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 22 18:26:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 22 Jun 2014 18:26:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1803) Deployments not being un-deploying when JUnit Category is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1803: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/3ded7d2612915b4db352d5f50aa8ab59f55835d7 > Deployments not being un-deploying when JUnit Category is used > --------------------------------------------------------------- > > Key: ARQ-1803 > URL: https://issues.jboss.org/browse/ARQ-1803 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Harness Integration > Affects Versions: 1.1.4.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 05:53:26 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 23 Jun 2014 05:53:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-286) Should support JUnit @Rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978489#comment-12978489 ] Stefan Miklosovic commented on ARQ-286: --------------------------------------- It seems to me that it is still failing in RunAsClient scenario. Consider this: {code} @RunWith(Arquillian.class) @RunAsClient public class TestCase { @Rule public ExpectedException e = ExpectedException.none(); @Test public void test() { e.expect(RuntimeException.class) throw new RuntimeException(); } } {code} Observing org.jboss.arquillian.test.spi.event.suite.After and org.jboss.arquillian.test.spi.event.suite.After still tells me that result.getStatus() == Status.FAILED is true. Should I file related jira or client mode was not treated yet? Thanks > Should support JUnit @Rules > --------------------------- > > Key: ARQ-286 > URL: https://issues.jboss.org/browse/ARQ-286 > Project: Arquillian > Issue Type: Feature Request > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. > It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 05:55:26 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 23 Jun 2014 05:55:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-286) Should support JUnit @Rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978489#comment-12978489 ] Stefan Miklosovic edited comment on ARQ-286 at 6/23/14 5:54 AM: ---------------------------------------------------------------- It seems to me that it is still failing in RunAsClient scenario. Consider this: {code} @RunWith(Arquillian.class) @RunAsClient public class TestCase { @Rule public ExpectedException e = ExpectedException.none(); @Test public void test() { e.expect(RuntimeException.class) throw new RuntimeException(); } } {code} Observing org.jboss.arquillian.test.spi.event.suite.After and org.jboss.arquillian.test.spi.TestResult still tells me that result.getStatus() == Status.FAILED is true. I am using {code} org.jboss.arquillian.junit arquillian-junit-container test {code} in the test project. Should I file related jira or client mode was not treated yet? Thanks was (Author: smikloso): It seems to me that it is still failing in RunAsClient scenario. Consider this: {code} @RunWith(Arquillian.class) @RunAsClient public class TestCase { @Rule public ExpectedException e = ExpectedException.none(); @Test public void test() { e.expect(RuntimeException.class) throw new RuntimeException(); } } {code} Observing org.jboss.arquillian.test.spi.event.suite.After and org.jboss.arquillian.test.spi.event.suite.After still tells me that result.getStatus() == Status.FAILED is true. Should I file related jira or client mode was not treated yet? Thanks > Should support JUnit @Rules > --------------------------- > > Key: ARQ-286 > URL: https://issues.jboss.org/browse/ARQ-286 > Project: Arquillian > Issue Type: Feature Request > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. > It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 09:08:24 2014 From: issues at jboss.org (Pramod Kankure (JIRA)) Date: Mon, 23 Jun 2014 09:08:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1777) Test hangs on remote Tomcat 6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978582#comment-12978582 ] Pramod Kankure commented on ARQ-1777: ------------------------------------- Aslak, yes I am referring to it. Thanks Pramod > Test hangs on remote Tomcat 6 > ----------------------------- > > Key: ARQ-1777 > URL: https://issues.jboss.org/browse/ARQ-1777 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Pramod Kankure > > I have observed that test hangs when executing on tomcat 6 remote container. > My arquillian.xml looks like below. ( I don't use authentication for jmx) > > xmlns="http://jboss.org/schema/arquillian" > xsi:schemaLocation="http://jboss.org/schema/arquillian > http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> > > > > > 1776 > localhost > 8090 > > > > > The test do stops with an error when the server is down or wrong HTTP port is specified. It does execute @deployment method of the test but never comes to execute the test method annoted with [~test.todd] -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 11:05:24 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 23 Jun 2014 11:05:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1741) Injector might throw unchecked TypeNotPresentException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978648#comment-12978648 ] Karel Piwko commented on ARQ-1741: ---------------------------------- That's exactly what I've meant. > Injector might throw unchecked TypeNotPresentException > ------------------------------------------------------ > > Key: ARQ-1741 > URL: https://issues.jboss.org/browse/ARQ-1741 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Priority: Minor > > *When*: > I call Injector.get().inject() > *And*: > Service to be injected is not on classpath > *Then*: > Arquillian throws TypeNotPresentException. This is fine, however it should be in API so when looking into code this is more obvious. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 11:47:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 23 Jun 2014 11:47:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1741) Injector might throw unchecked TypeNotPresentException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978665#comment-12978665 ] Aslak Knutsen commented on ARQ-1741: ------------------------------------ Are you trying to handle a TypeNotPresentException? > Injector might throw unchecked TypeNotPresentException > ------------------------------------------------------ > > Key: ARQ-1741 > URL: https://issues.jboss.org/browse/ARQ-1741 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Priority: Minor > > *When*: > I call Injector.get().inject() > *And*: > Service to be injected is not on classpath > *Then*: > Arquillian throws TypeNotPresentException. This is fine, however it should be in API so when looking into code this is more obvious. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 11:51:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 23 Jun 2014 11:51:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-286) Should support JUnit @Rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978666#comment-12978666 ] Aslak Knutsen commented on ARQ-286: ----------------------------------- The client side doesn't fail, as far as Rule support it works just fine. :) You're talking about this ARQ-181 which is a separate issue and not related to Rules only. Working on that as we speak. Got it working for either incontainer or runasclient atm, but struggling with both. :) > Should support JUnit @Rules > --------------------------- > > Key: ARQ-286 > URL: https://issues.jboss.org/browse/ARQ-286 > Project: Arquillian > Issue Type: Feature Request > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. > It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 17:20:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 23 Jun 2014 17:20:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1804: ------------------------------- Description: When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. TestNG @Test(expectedException=Exception.class) @ExpectedException(Exception.class) Follow up with TestNG to see how this can be done.. was: When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. JUnit @Test(expected=Exception.class) TestNG @Test(expectedException=Exception.class) @ExpectedException(Exception.class) Follow up with TestNG and JUnit to see how this can be done.. > When using @Test expected exception, the internal state of the TestResult is unknown - TestNG > --------------------------------------------------------------------------------------------- > > Key: ARQ-1804 > URL: https://issues.jboss.org/browse/ARQ-1804 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 17:20:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 23 Jun 2014 17:20:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1804: ---------------------------------- Summary: When using @Test expected exception, the internal state of the TestResult is unknown - TestNG Key: ARQ-1804 URL: https://issues.jboss.org/browse/ARQ-1804 Project: Arquillian Issue Type: Bug Components: Test Harness Integration Reporter: Aslak Knutsen Priority: Minor Fix For: 1.1.5.Final When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. JUnit @Test(expected=Exception.class) TestNG @Test(expectedException=Exception.class) @ExpectedException(Exception.class) Follow up with TestNG and JUnit to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 17:22:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 23 Jun 2014 17:22:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1804: ------------------------------- Fix Version/s: (was: 1.1.5.Final) > When using @Test expected exception, the internal state of the TestResult is unknown - TestNG > --------------------------------------------------------------------------------------------- > > Key: ARQ-1804 > URL: https://issues.jboss.org/browse/ARQ-1804 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Priority: Minor > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 17:22:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 23 Jun 2014 17:22:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-181) When using @Test expected exception, the internal state of the TestResult is unknown - JUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-181: ------------------------------ Summary: When using @Test expected exception, the internal state of the TestResult is unknown - JUnit (was: When using @Test expected exception, the internal state of the TestResult is unknown) > When using @Test expected exception, the internal state of the TestResult is unknown - JUnit > -------------------------------------------------------------------------------------------- > > Key: ARQ-181 > URL: https://issues.jboss.org/browse/ARQ-181 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > JUnit > @Test(expected=Exception.class) > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG and JUnit to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 17:22:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 23 Jun 2014 17:22:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-181) When using @Test expected exception, the internal state of the TestResult is unknown - JUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen reassigned ARQ-181: --------------------------------- Assignee: Aslak Knutsen > When using @Test expected exception, the internal state of the TestResult is unknown - JUnit > -------------------------------------------------------------------------------------------- > > Key: ARQ-181 > URL: https://issues.jboss.org/browse/ARQ-181 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > JUnit > @Test(expected=Exception.class) > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG and JUnit to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 17:22:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 23 Jun 2014 17:22:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-181) When using @Test expected exception, the internal state of the TestResult is unknown - JUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-181. ------------------------------- Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/3922dbb566948ffd322cdaac42c5f7cd999b2fa3 > When using @Test expected exception, the internal state of the TestResult is unknown - JUnit > -------------------------------------------------------------------------------------------- > > Key: ARQ-181 > URL: https://issues.jboss.org/browse/ARQ-181 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > JUnit > @Test(expected=Exception.class) > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG and JUnit to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 23 17:44:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 23 Jun 2014 17:44:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1607) Please avoid using arquillian.launch files, it makes Eclipse generate error logs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1607. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream; https://github.com/arquillian/arquillian-core/commit/47b0c3ff0f73716ec31c9be403fb19d5460835b2 > Please avoid using arquillian.launch files, it makes Eclipse generate error logs > -------------------------------------------------------------------------------- > > Key: ARQ-1607 > URL: https://issues.jboss.org/browse/ARQ-1607 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: Eclipse > Reporter: Fred Bricon > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When imported in Eclipse, projects containing arquillian.launch files make Eclipse barf as it expects a valid Eclipse Launch configuration xml file. > It's just an error in the .metadata/.log, but the sight of such ugly stacktraces could be frightening/annoying for some > {noformat} > !MESSAGE org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Contenu non autoris? dans le prologue. occurred while reading launch configuration file: D:\tmp\arquillian-examples\arquillian-persistence-tutorial\target\test-classes\arquillian.launch. > !STACK 0 > org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Contenu non autoris? dans le prologue. > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198) > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441) > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368) > at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1388) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:998) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:489) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) > at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) > at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:237) > at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:300) > at org.eclipse.debug.internal.core.LaunchManager.createInfoFromXML(LaunchManager.java:929) > at org.eclipse.debug.internal.core.LaunchManager.getInfo(LaunchManager.java:1353) > at org.eclipse.debug.internal.core.LaunchConfiguration.getInfo(LaunchConfiguration.java:453) > at org.eclipse.debug.internal.core.LaunchConfiguration.getType(LaunchConfiguration.java:617) > at org.eclipse.debug.internal.core.LaunchManager.isValid(LaunchManager.java:2081) > at org.eclipse.debug.internal.core.LaunchManager.launchConfigurationAdded(LaunchManager.java:2104) > at org.eclipse.debug.internal.core.LaunchManager$LaunchManagerVisitor.visit(LaunchManager.java:382) > {noformat} > From IRC > {quote} > (15:46:37) fbricon: hey aslak, I'm looking at a some maven projects containing some arquillian.launch files > (15:47:18) fbricon: eclipse treats these as Launch configuration files and complains they're malformed xml > (15:47:38) fbricon: do the files need to be .launch? > 15:47:58) aslak: fbricon hehe yea.. noticed that as well.. > (15:48:22) aslak: it ended up being called arquillian.launch because that's the name of the -D property that does the same > (15:48:50) aslak: fbricon could you file an issue on this.. I'll add support for arquillian.launch.properties or arquillian-launch or similar > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 04:16:27 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 24 Jun 2014 04:16:27 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1679) When expected exception is thrown in test method, reporter should not report it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1679: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha4 > When expected exception is thrown in test method, reporter should not report it > ------------------------------------------------------------------------------- > > Key: ARQ-1679 > URL: https://issues.jboss.org/browse/ARQ-1679 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha4 > > > When I have > {code} > @Test(expected = SomeException.class) > public void someTest() { > throw new SomeException("this is test exception"); > } > {code} > It should not appear in resulting report. Take JUnit @Rule into account as well. > Take into consideration various test frameworks. > https://github.com/arquillian/arquillian-recorder/blob/1.0.0.Alpha1/arquillian-recorder-reporter/arquillian-recorder-reporter-impl/src/main/java/org/arquillian/recorder/reporter/impl/ReporterLifecycleObserver.java#L164-L168 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 04:18:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 24 Jun 2014 04:18:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1679) When expected exception is thrown in test method, reporter should not report it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1679. ------------------------------------ Resolution: Done This will be repaired with the release of 1.1.5.Final of Core. > When expected exception is thrown in test method, reporter should not report it > ------------------------------------------------------------------------------- > > Key: ARQ-1679 > URL: https://issues.jboss.org/browse/ARQ-1679 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha4 > > > When I have > {code} > @Test(expected = SomeException.class) > public void someTest() { > throw new SomeException("this is test exception"); > } > {code} > It should not appear in resulting report. Take JUnit @Rule into account as well. > Take into consideration various test frameworks. > https://github.com/arquillian/arquillian-recorder/blob/1.0.0.Alpha1/arquillian-recorder-reporter/arquillian-recorder-reporter-impl/src/main/java/org/arquillian/recorder/reporter/impl/ReporterLifecycleObserver.java#L164-L168 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 04:24:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 24 Jun 2014 04:24:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1710) Integrate desktop video recorder project to recorder extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1710. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha4 Resolution: Won't Fix [~kpiwko] Desktop recorder extension is already integrated however it will never be released to Central due to incompatibility of dependency project (Xuggler is GPL licenced, Arquillian is Apachce licenced) so you need to build it on your own. This information was already added to README of desktop recorder module. I am resolving this as "won't fix". Feel free to change it to whatever you think is more suitable. > Integrate desktop video recorder project to recorder extension > -------------------------------------------------------------- > > Key: ARQ-1710 > URL: https://issues.jboss.org/browse/ARQ-1710 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 04:28:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 24 Jun 2014 04:28:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1716) Provide support for TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1716: -------------------------------------- Assignee: Stefan Miklosovic > Provide support for TestNG > -------------------------- > > Key: ARQ-1716 > URL: https://issues.jboss.org/browse/ARQ-1716 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Stefan Miklosovic > > Reporter extension does not work properly with TestNG. For example when test fails with exception, it causes to throw exception by reporter as well: > {code} > arquillianAfterTest(org.richfaces.tests.showcase.ajax.TestAjax) Time elapsed: 5.797 sec <<< FAILURE! > java.lang.IllegalStateException: Test method is not annotated with @Test annotation > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.isThrowingExpectedException(ReporterLifecycleObserver.java:262) > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.observeAfterTest(ReporterLifecycleObserver.java:178) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterTest(Arquillian.java:149) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:753) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1178) > at org.testng.TestRunner.privateRun(TestRunner.java:757) > at org.testng.TestRunner.run(TestRunner.java:608) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) > at org.testng.TestNG.run(TestNG.java:999) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:69) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:120) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:104) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} > Its because it is tested only for {{@Test}} from junit package. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 04:28:25 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 24 Jun 2014 04:28:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1716) Provide support for TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1716: ----------------------------------- Assignee: Juraj H?ska (was: Stefan Miklosovic) > Provide support for TestNG > -------------------------- > > Key: ARQ-1716 > URL: https://issues.jboss.org/browse/ARQ-1716 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > Reporter extension does not work properly with TestNG. For example when test fails with exception, it causes to throw exception by reporter as well: > {code} > arquillianAfterTest(org.richfaces.tests.showcase.ajax.TestAjax) Time elapsed: 5.797 sec <<< FAILURE! > java.lang.IllegalStateException: Test method is not annotated with @Test annotation > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.isThrowingExpectedException(ReporterLifecycleObserver.java:262) > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.observeAfterTest(ReporterLifecycleObserver.java:178) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterTest(Arquillian.java:149) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:753) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1178) > at org.testng.TestRunner.privateRun(TestRunner.java:757) > at org.testng.TestRunner.run(TestRunner.java:608) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) > at org.testng.TestNG.run(TestNG.java:999) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:69) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:120) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:104) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} > Its because it is tested only for {{@Test}} from junit package. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 04:37:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 24 Jun 2014 04:37:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1716) Provide support for TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960090#comment-12960090 ] Stefan Miklosovic edited comment on ARQ-1716 at 6/24/14 4:36 AM: ----------------------------------------------------------------- This will be autoresolved by ARQ-1804 when it will be done in Arq Core. was (Author: smikloso): This will be autoresolved by ARQ-1679 when it will be done in Arq Core. > Provide support for TestNG > -------------------------- > > Key: ARQ-1716 > URL: https://issues.jboss.org/browse/ARQ-1716 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > Reporter extension does not work properly with TestNG. For example when test fails with exception, it causes to throw exception by reporter as well: > {code} > arquillianAfterTest(org.richfaces.tests.showcase.ajax.TestAjax) Time elapsed: 5.797 sec <<< FAILURE! > java.lang.IllegalStateException: Test method is not annotated with @Test annotation > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.isThrowingExpectedException(ReporterLifecycleObserver.java:262) > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.observeAfterTest(ReporterLifecycleObserver.java:178) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterTest(Arquillian.java:149) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:753) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1178) > at org.testng.TestRunner.privateRun(TestRunner.java:757) > at org.testng.TestRunner.run(TestRunner.java:608) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) > at org.testng.TestNG.run(TestNG.java:999) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:69) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:120) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:104) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} > Its because it is tested only for {{@Test}} from junit package. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 04:45:27 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 24 Jun 2014 04:45:27 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1701: -------------------------------------- Assignee: Stefan Miklosovic > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 05:05:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 24 Jun 2014 05:05:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1751) Implement web-based console which streams reporting events in realtime In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1751: -------------------------------------- Assignee: Stefan Miklosovic > Implement web-based console which streams reporting events in realtime > ---------------------------------------------------------------------- > > Key: ARQ-1751 > URL: https://issues.jboss.org/browse/ARQ-1751 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Labels: hack-idea > > Every fired reporter event would be observed by additional observer which would send it to REST end point of some running "reporter server" so when user starts some test, he would see in web console in ordinary browser how some test is going. > Reporter would "stream" reporting events to console ui so user would not have to wait until the whole test is done but he would see how test is going on in realtime. > This can be handy particulary in CI environment. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 07:29:25 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 24 Jun 2014 07:29:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1701: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha4 > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha4 > > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 07:31:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 24 Jun 2014 07:31:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1701. ------------------------------------ Resolution: Done > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha4 > > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 08:46:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 08:46:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1751) Implement web-based console which streams reporting events in realtime In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978889#comment-12978889 ] Aslak Knutsen commented on ARQ-1751: ------------------------------------ This is a _almost_ working prototype from DevNation hackfest; https://github.com/aslakknutsen/arquillian-recorder/tree/ARQ-1751 The missing parts; * probably integrate bowler with Maven to build the UI JS parts automatically * some missmatch in URL used by the UI and backend atm * possible some missmtach in the format used General improvements require some more changes in recorder core. e.g.; * Should the same JAX-B model be used on Client and Container side? * JAX-B in general generates XML, XML is hell'ish in a JS client ** Currently worked around by XML from Test client to Server, and Gson converted jax-b model from Server to JS client * The full report is pushed to server for each @Test * Missing image upload. > Implement web-based console which streams reporting events in realtime > ---------------------------------------------------------------------- > > Key: ARQ-1751 > URL: https://issues.jboss.org/browse/ARQ-1751 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Labels: hack-idea > > Every fired reporter event would be observed by additional observer which would send it to REST end point of some running "reporter server" so when user starts some test, he would see in web console in ordinary browser how some test is going. > Reporter would "stream" reporting events to console ui so user would not have to wait until the whole test is done but he would see how test is going on in realtime. > This can be handy particulary in CI environment. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 11:17:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 11:17:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1804: ------------------------------- Fix Version/s: 1.1.5.Final > When using @Test expected exception, the internal state of the TestResult is unknown - TestNG > --------------------------------------------------------------------------------------------- > > Key: ARQ-1804 > URL: https://issues.jboss.org/browse/ARQ-1804 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:48:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 24 Jun 2014 12:48:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978999#comment-12978999 ] Juraj H?ska commented on ARQ-1804: ---------------------------------- I have verified it with current {{1.1.5.Final-SNAPSHOT}} Arquillian core, and it works for me. Now, the reporter extension is not reporting an expected exception. I have tested it in [this project, on this branch|https://github.com/richfaces/richfaces-qa/tree/drone2Trying/showcase-ftest]. To run the test issue: {code} mvn clean verify -Pwildfly-managed-8-1 -Dtest=TestAjax {code} > When using @Test expected exception, the internal state of the TestResult is unknown - TestNG > --------------------------------------------------------------------------------------------- > > Key: ARQ-1804 > URL: https://issues.jboss.org/browse/ARQ-1804 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:50:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:50:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1804. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream, https://github.com/arquillian/arquillian-core/commit/ade8eb99b3d4c808c75f56a7023de7feb8977bbf > When using @Test expected exception, the internal state of the TestResult is unknown - TestNG > --------------------------------------------------------------------------------------------- > > Key: ARQ-1804 > URL: https://issues.jboss.org/browse/ARQ-1804 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:50:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 24 Jun 2014 12:50:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978999#comment-12978999 ] Juraj H?ska edited comment on ARQ-1804 at 6/24/14 12:49 PM: ------------------------------------------------------------ I have verified it with current {{1.1.5.Final-SNAPSHOT}} Arquillian core, and it works for me. Now, the reporter extension is not reporting an expected exception. I have tested it in [this project, on this branch|https://github.com/richfaces/richfaces-qa/tree/drone2Trying/showcase-ftest]. To run the test issue: {code} mvn clean verify -Pwildfly-managed-8-1 -Dtest=TestAjax {code} The [test file|https://github.com/richfaces/richfaces-qa/tree/drone2Trying/showcase-ftest], one test is expected to fail. was (Author: jhuska): I have verified it with current {{1.1.5.Final-SNAPSHOT}} Arquillian core, and it works for me. Now, the reporter extension is not reporting an expected exception. I have tested it in [this project, on this branch|https://github.com/richfaces/richfaces-qa/tree/drone2Trying/showcase-ftest]. To run the test issue: {code} mvn clean verify -Pwildfly-managed-8-1 -Dtest=TestAjax {code} > When using @Test expected exception, the internal state of the TestResult is unknown - TestNG > --------------------------------------------------------------------------------------------- > > Key: ARQ-1804 > URL: https://issues.jboss.org/browse/ARQ-1804 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1801) @Before not called with arquillian-junit-standalone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1801. ------------------------------ > @Before not called with arquillian-junit-standalone > --------------------------------------------------- > > Key: ARQ-1801 > URL: https://issues.jboss.org/browse/ARQ-1801 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > When using > {code} > > org.jboss.arquillian.junit > arquillian-junit-standalone > 1.1.4.Final > > {code} > @BeforeClass and @Before are not called. > Using arquillian-junit-container they are. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1742) Exception thrown before BeforeSuite event are not reported to user. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1742. ------------------------------ > Exception thrown before BeforeSuite event are not reported to user. > ------------------------------------------------------------------- > > Key: ARQ-1742 > URL: https://issues.jboss.org/browse/ARQ-1742 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > *When*: > My extensions observes ManagerStarted event and something gets wrong and an exception is thrown. > *Then*: > Arquillian (Or rather JUnit) silently ignores the exception, causing subsequent children runs to be ignored: > https://github.com/arquillian/arquillian-core/blob/master/junit/core/src/main/java/org/jboss/arquillian/junit/Arquillian.java#L95 > This behavior should be improved. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1606) Support deploymentExportPath to export Exploded In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1606. ------------------------------ > Support deploymentExportPath to export Exploded > ----------------------------------------------- > > Key: ARQ-1606 > URL: https://issues.jboss.org/browse/ARQ-1606 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.2.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Currently deploymentExportPath will export a Zipped file, but the reason for exporting it is to see the content. Allow to export as exploded. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1607) Please avoid using arquillian.launch files, it makes Eclipse generate error logs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1607. ------------------------------ > Please avoid using arquillian.launch files, it makes Eclipse generate error logs > -------------------------------------------------------------------------------- > > Key: ARQ-1607 > URL: https://issues.jboss.org/browse/ARQ-1607 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: Eclipse > Reporter: Fred Bricon > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When imported in Eclipse, projects containing arquillian.launch files make Eclipse barf as it expects a valid Eclipse Launch configuration xml file. > It's just an error in the .metadata/.log, but the sight of such ugly stacktraces could be frightening/annoying for some > {noformat} > !MESSAGE org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Contenu non autoris? dans le prologue. occurred while reading launch configuration file: D:\tmp\arquillian-examples\arquillian-persistence-tutorial\target\test-classes\arquillian.launch. > !STACK 0 > org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Contenu non autoris? dans le prologue. > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198) > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441) > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368) > at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1388) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:998) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:489) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) > at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) > at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:237) > at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:300) > at org.eclipse.debug.internal.core.LaunchManager.createInfoFromXML(LaunchManager.java:929) > at org.eclipse.debug.internal.core.LaunchManager.getInfo(LaunchManager.java:1353) > at org.eclipse.debug.internal.core.LaunchConfiguration.getInfo(LaunchConfiguration.java:453) > at org.eclipse.debug.internal.core.LaunchConfiguration.getType(LaunchConfiguration.java:617) > at org.eclipse.debug.internal.core.LaunchManager.isValid(LaunchManager.java:2081) > at org.eclipse.debug.internal.core.LaunchManager.launchConfigurationAdded(LaunchManager.java:2104) > at org.eclipse.debug.internal.core.LaunchManager$LaunchManagerVisitor.visit(LaunchManager.java:382) > {noformat} > From IRC > {quote} > (15:46:37) fbricon: hey aslak, I'm looking at a some maven projects containing some arquillian.launch files > (15:47:18) fbricon: eclipse treats these as Launch configuration files and complains they're malformed xml > (15:47:38) fbricon: do the files need to be .launch? > 15:47:58) aslak: fbricon hehe yea.. noticed that as well.. > (15:48:22) aslak: it ended up being called arquillian.launch because that's the name of the -D property that does the same > (15:48:50) aslak: fbricon could you file an issue on this.. I'll add support for arquillian.launch.properties or arquillian-launch or similar > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1796) Regression: JUnit ExpectedException is not handled correctly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1796. ------------------------------ > Regression: JUnit ExpectedException is not handled correctly > ------------------------------------------------------------ > > Key: ARQ-1796 > URL: https://issues.jboss.org/browse/ARQ-1796 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Rich DiCroce > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > I have many tests using JUnit's ExcpectedException rule. In Arquillian 1.1.3, these tests worked perfectly. When I tried to update to 1.1.4, they broke. It seems like Arquillian now catches the exceptions before ExpectedException does, and propagates them back to the client. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1772) Arquillian Debug does not print real event class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1772. ------------------------------ > Arquillian Debug does not print real event class > ------------------------------------------------ > > Key: ARQ-1772 > URL: https://issues.jboss.org/browse/ARQ-1772 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > When using inheritance to define events, Arquillian Debug prints out following: > {code} > (E) PrepareDrone > (O) EventRegisterObserver.register > (O) DroneConfigurator.prepareDrone > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) Before > (O) EventRegisterObserver.register > (O) DroneLifecycleManager.before > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > {code} > Which is not really super useful, as debug log can't show what actual events were fired. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1773. ------------------------------ > JUnittests pass when exception is thrown from @Before-annotated method > ---------------------------------------------------------------------- > > Key: ARQ-1773 > URL: https://issues.jboss.org/browse/ARQ-1773 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Mattias Persson > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > Attachments: arquillian_test_should_fail.zip > > > When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:27 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:27 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1758) Test passes although it fails unexpectedly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1758. ------------------------------ > Test passes although it fails unexpectedly > ------------------------------------------ > > Key: ARQ-1758 > URL: https://issues.jboss.org/browse/ARQ-1758 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Robert Panzer > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > Attachments: debug.png > > > I have an erronous test class that cannot be loaded in the container due to a NoClassDefFoundError. (A dependent class is missing.) > The test passes unexpectedly and all test methods are reported to have passed although log entries or SystemOuts show that the methods are actually never invoked. > The problem seems to be a regression that came with the last release. > In JUnitTestRunner the TestResults exception is overwritten with null in such a case. > I will attach a screenshot of the debugger showing that. > I also have a try of a patch that I will link as soon as I prepared the pull request on github. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:27 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:27 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1803) Deployments not being un-deploying when JUnit Category is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1803. ------------------------------ > Deployments not being un-deploying when JUnit Category is used > --------------------------------------------------------------- > > Key: ARQ-1803 > URL: https://issues.jboss.org/browse/ARQ-1803 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Harness Integration > Affects Versions: 1.1.4.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:28 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:28 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1802) Expose the underlying HTTPConnection used by Servlet protocol to allow new protocols manipulation access. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1802. ------------------------------ > Expose the underlying HTTPConnection used by Servlet protocol to allow new protocols manipulation access. > --------------------------------------------------------------------------------------------------------- > > Key: ARQ-1802 > URL: https://issues.jboss.org/browse/ARQ-1802 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.4.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:28 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:28 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-181) When using @Test expected exception, the internal state of the TestResult is unknown - JUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-181. ----------------------------- > When using @Test expected exception, the internal state of the TestResult is unknown - JUnit > -------------------------------------------------------------------------------------------- > > Key: ARQ-181 > URL: https://issues.jboss.org/browse/ARQ-181 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > JUnit > @Test(expected=Exception.class) > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG and JUnit to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:28 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:28 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1804) When using @Test expected exception, the internal state of the TestResult is unknown - TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1804. ------------------------------ > When using @Test expected exception, the internal state of the TestResult is unknown - TestNG > --------------------------------------------------------------------------------------------- > > Key: ARQ-1804 > URL: https://issues.jboss.org/browse/ARQ-1804 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. > TestNG > @Test(expectedException=Exception.class) > @ExpectedException(Exception.class) > Follow up with TestNG to see how this can be done.. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:28 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:28 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1437) NPE in ExceptionProxy.readExternal() for root cause leads to deserializationProblem = true In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1437. ------------------------------ > NPE in ExceptionProxy.readExternal() for root cause leads to deserializationProblem = true > ------------------------------------------------------------------------------------------ > > Key: ARQ-1437 > URL: https://issues.jboss.org/browse/ARQ-1437 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.2.Final, 1.1.0.Final > Reporter: Falko M. > Assignee: Aslak Knutsen > Priority: Minor > Fix For: 1.1.5.Final > > > See line 199 (for 1.0.2.Final): > {code} > // reset the cause, so we can de-serialize them individual > SecurityActions.setFieldValue(Throwable.class, original, "cause", causeProxy.createException()); > {code} > For the root cause of an exception, {{causeProxy}} will always be {{null}} and so a {{NullPointerException}} is thrown. > As the code is wrapped in a try block with follwoing catch block: > {code} > catch (Throwable e) // ClassNotFoundExcpetion / NoClassDefFoundError > { > // ignore, could not load class on client side, move on and create a fake 'proxy' later > deserializationProblem = true; > } > {code} > the NPE is caught and is "expected" to be a {{ClassNotFoundExcpetion}} or {{NoClassDefFoundError}} which is clearly not the case. > *Possible fix:* > {{original.cause}} should only be overwritten when {{causeProxy}} is *not* null. > *More context information:* > I came across this problem while trying to find the reason for an unexpected {{ArquillianProxyException}}: > {code}org.jboss.arquillian.test.spi.ArquillianProxyException: javax.ejb.EJBException : javax.persistence.OptimisticLockException [Proxied because : Original exception not deserilizable, ClassNotFoundException]{code} > The root problem was not the NPE, but the {{ClassNotFoundException}} mislead me and so I debugged {{ExceptionProxy}}. > I my case there is an {{InvalidClassException}} because of an older hibernate version on the client side. > +So that is another problem of {{ExceptionProxy}} as it assumes that only {{ClassNotFoundExcpetion}} or {{NoClassDefFoundError}} can occur!+ -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:52:29 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 24 Jun 2014 12:52:29 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-286) Should support JUnit @Rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-286. ----------------------------- > Should support JUnit @Rules > --------------------------- > > Key: ARQ-286 > URL: https://issues.jboss.org/browse/ARQ-286 > Project: Arquillian > Issue Type: Feature Request > Components: Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.5.Final > > > Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. > It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 12:58:24 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 24 Jun 2014 12:58:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1741) Injector might throw unchecked TypeNotPresentException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979005#comment-12979005 ] Karel Piwko commented on ARQ-1741: ---------------------------------- I don't think so. It would just be nice to indicate that via API signature so people might react to it. > Injector might throw unchecked TypeNotPresentException > ------------------------------------------------------ > > Key: ARQ-1741 > URL: https://issues.jboss.org/browse/ARQ-1741 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > Priority: Minor > > *When*: > I call Injector.get().inject() > *And*: > Service to be injected is not on classpath > *Then*: > Arquillian throws TypeNotPresentException. This is fine, however it should be in API so when looking into code this is more obvious. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 24 17:50:24 2014 From: issues at jboss.org (Bernard Labno (JIRA)) Date: Tue, 24 Jun 2014 17:50:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1135) standard-sockets -> http -> bound-port is undefined In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979078#comment-12979078 ] Bernard Labno commented on ARQ-1135: ------------------------------------ Might be related to this https://issues.jboss.org/browse/AS7-3607 Try this: {code:xml} /home/bernard/bin/jboss-as-7.1.1.Final -Djava.net.preferIPv4Stack=true {code} > standard-sockets -> http -> bound-port is undefined > --------------------------------------------------- > > Key: ARQ-1135 > URL: https://issues.jboss.org/browse/ARQ-1135 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Mac Os X, open JDK 1.7 > Reporter: Stefan Frank > Labels: mac, openjdk > > I get the following exception whenever I start an arquillian-test. It already happens after @Deployment has built a proper shrinkwrap. I'm trying to use the {code}{code} so it looks like there are issues while connecting to the jboss. Similar tests run fine on another platform (windows) and another jdk(oracles jdk 1.7) - so maybe this has to do something with the platform or the jdk?! > {code} > java.lang.RuntimeException: java.lang.IllegalStateException: standard-sockets -> http -> bound-port is undefined > at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:222) > at org.jboss.as.arquillian.container.ManagementClient.getWebUri(ManagementClient.java:111) > at org.jboss.as.arquillian.container.ManagementClient.getDeploymentMetaData(ManagementClient.java:117) > at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:150) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > Caused by: java.lang.IllegalStateException: standard-sockets -> http -> bound-port is undefined > at org.jboss.as.arquillian.container.ManagementClient.defined(ManagementClient.java:193) > at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:218) > ... 90 more > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 07:39:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 25 Jun 2014 07:39:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1716) Provide support for TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1716. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha4 Resolution: Done > Provide support for TestNG > -------------------------- > > Key: ARQ-1716 > URL: https://issues.jboss.org/browse/ARQ-1716 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: recorder_1.0.0.Alpha4 > > > Reporter extension does not work properly with TestNG. For example when test fails with exception, it causes to throw exception by reporter as well: > {code} > arquillianAfterTest(org.richfaces.tests.showcase.ajax.TestAjax) Time elapsed: 5.797 sec <<< FAILURE! > java.lang.IllegalStateException: Test method is not annotated with @Test annotation > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.isThrowingExpectedException(ReporterLifecycleObserver.java:262) > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.observeAfterTest(ReporterLifecycleObserver.java:178) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterTest(Arquillian.java:149) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:753) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1178) > at org.testng.TestRunner.privateRun(TestRunner.java:757) > at org.testng.TestRunner.run(TestRunner.java:608) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) > at org.testng.TestNG.run(TestNG.java:999) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:69) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:120) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:104) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} > Its because it is tested only for {{@Test}} from junit package. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 16:07:24 2014 From: issues at jboss.org (=?UTF-8?Q?Thomas_K=C3=BCstermann_=28JIRA=29?=) Date: Wed, 25 Jun 2014 16:07:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1779) Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979408#comment-12979408 ] Thomas K?stermann commented on ARQ-1779: ---------------------------------------- I just read the release announcement of Arquillian 1.1.5.Final {quote} Fixed false positives with JUnit from 1.1.4.Final Arquillian Core 1.1.4.Final had a nasty bug where it would ?erase? some special exception cases that could happen In Container, that gave the Client side the wrong result. This has now been fixed. Expected exceptions, Assumption and Injection errors should now be reported correctly(Both when using the @Rule and the @Test.expected variants). {quote} After upgrading to the new version, the false positive described here is gone. This issue can be closed as duplicate of ARQ-1758 I think. > Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter > ----------------------------------------------------------------------------------- > > Key: ARQ-1779 > URL: https://issues.jboss.org/browse/ARQ-1779 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Thomas K?stermann > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Forum reference: https://community.jboss.org/message/874117 > The following test case succeeds (green bar) although it should fail: > {code:java} > @RunWith(Arquillian.class) > @DataSource("java:oracleDS") > @Cleanup(phase=TestExecutionPhase.NONE) > @ApplyScriptBefore("deploy-db-functionality.sql") > @ApplyScriptAfter("undeploy-db-functionality.sql") > public class PersistenceIT { > // @Deployment ... > > @Test > @ApplyScriptBefore("trigger-db-functionality.sql") > public void shouldFail() { > Assert.fail("should fail, but doesn't"); > } > } > {code} > Removing class level annotations does not work either: > {code:java} > @Test > @ApplyScriptBefore({ "deploy-db-functionality.sql", "trigger-db-functionality.sql" }) > @ApplyScriptAfter("undeploy-db-functionality.sql") > public void shouldFail() { ... } > {code} > What actually works is to use only one ApplyScriptBefore / ApplyScriptAfter annotation per test, each with only one script to execute. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 04:32:40 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 26 Jun 2014 04:32:40 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1751) Implement web-based console which streams reporting events in realtime In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979575#comment-12979575 ] Stefan Miklosovic commented on ARQ-1751: ---------------------------------------- Regarding of XML report, you could export it directly to JSON exporter (1) https://github.com/arquillian/arquillian-recorder/blob/master/arquillian-recorder-reporter/arquillian-recorder-reporter-impl/src/main/java/org/arquillian/recorder/reporter/exporter/impl/JSONExporter.java The problem with full report pushing is that reporter constructs that JAXB model as a tree-like structure. If you want it more granular, I guess you would have to fire reporting event more frequently only with reporting snippets done after the last report action and somehow "append" them in a browser. Image upload can be done later in the next iterations. I would like to see this module in Reporter Beta1, Alpha4 is going to be release in a week I hope, I'll look at this in august. > Implement web-based console which streams reporting events in realtime > ---------------------------------------------------------------------- > > Key: ARQ-1751 > URL: https://issues.jboss.org/browse/ARQ-1751 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Labels: hack-idea > > Every fired reporter event would be observed by additional observer which would send it to REST end point of some running "reporter server" so when user starts some test, he would see in web console in ordinary browser how some test is going. > Reporter would "stream" reporting events to console ui so user would not have to wait until the whole test is done but he would see how test is going on in realtime. > This can be handy particulary in CI environment. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 04:54:25 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 26 Jun 2014 04:54:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1751) Implement web-based console which streams reporting events in realtime In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979581#comment-12979581 ] Stefan Miklosovic commented on ARQ-1751: ---------------------------------------- Another idea is to make animated GIFs from recorded videos and stream them as well. You would in theory watch videos of test methods in a browser while your test is in fact still running as it would not have to be finished yet :) > Implement web-based console which streams reporting events in realtime > ---------------------------------------------------------------------- > > Key: ARQ-1751 > URL: https://issues.jboss.org/browse/ARQ-1751 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Labels: hack-idea > > Every fired reporter event would be observed by additional observer which would send it to REST end point of some running "reporter server" so when user starts some test, he would see in web console in ordinary browser how some test is going. > Reporter would "stream" reporting events to console ui so user would not have to wait until the whole test is done but he would see how test is going on in realtime. > This can be handy particulary in CI environment. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 09:05:23 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 09:05:23 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1805) Create individual transactions per @Before/@Test/@After lifecycle In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1805: ---------------------------------- Summary: Create individual transactions per @Before/@Test/@After lifecycle Key: ARQ-1805 URL: https://issues.jboss.org/browse/ARQ-1805 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Transaction Affects Versions: transaction_1.0.1.Final Reporter: Aslak Knutsen Fix For: transaction_1.0.0.next -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 10:06:23 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 10:06:23 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1806) Disable failing Spring test due to unintended transactions behavior In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1806: ---------------------------------- Summary: Disable failing Spring test due to unintended transactions behavior Key: ARQ-1806 URL: https://issues.jboss.org/browse/ARQ-1806 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Spring Affects Versions: spring_1.0.0.Beta2 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: spring_1.0.0.next -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 10:08:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 10:08:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1806) Disable failing Spring test due to unintended transactions behavior In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979682#comment-12979682 ] Aslak Knutsen commented on ARQ-1806: ------------------------------------ Re-enable when this is fixed > Disable failing Spring test due to unintended transactions behavior > ------------------------------------------------------------------- > > Key: ARQ-1806 > URL: https://issues.jboss.org/browse/ARQ-1806 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Spring > Affects Versions: spring_1.0.0.Beta2 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: spring_1.0.0.next > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 10:12:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 10:12:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1806) Disable failing Spring test due to unintended transactions behavior In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1806. -------------------------------- Resolution: Done pushed upstream https://github.com/arquillian/arquillian-extension-spring/commit/86427f1dfa7cdcdfdffd0619d8ea85765c421686 > Disable failing Spring test due to unintended transactions behavior > ------------------------------------------------------------------- > > Key: ARQ-1806 > URL: https://issues.jboss.org/browse/ARQ-1806 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Spring > Affects Versions: spring_1.0.0.Beta2 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: spring_1.0.0.next > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 10:18:25 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 26 Jun 2014 10:18:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1805) Create individual transactions per @Before/@Test/@After lifecycle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-1805: ----------------------------------- Assignee: Bartosz Majsak > Create individual transactions per @Before/@Test/@After lifecycle > ----------------------------------------------------------------- > > Key: ARQ-1805 > URL: https://issues.jboss.org/browse/ARQ-1805 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Transaction > Affects Versions: transaction_1.0.1.Final > Reporter: Aslak Knutsen > Assignee: Bartosz Majsak > Fix For: transaction_1.0.0.next > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 11:33:25 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 26 Jun 2014 11:33:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1718) Simple way to test on real device without the need to use serial id In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1718: ----------------------------------- Fix Version/s: droidium_1.0.0.Beta1 > Simple way to test on real device without the need to use serial id > ------------------------------------------------------------------- > > Key: ARQ-1718 > URL: https://issues.jboss.org/browse/ARQ-1718 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Reporter: Tadeas Kriz > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Beta1 > > > There should be a way to simply test on device, without the need to use serial id, if only one device is connected. Adb has this functionality (if only one device (real or emulated) is connected, it uses it, or with -d switch to use real device (-e for emulated one)). Droidium should also allow this and quit with error if no serial id is specified, but more devices are connected. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 11:33:25 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 26 Jun 2014 11:33:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1718) Simple way to test on real device without the need to use serial id In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1718. ------------------------------------ Resolution: Done > Simple way to test on real device without the need to use serial id > ------------------------------------------------------------------- > > Key: ARQ-1718 > URL: https://issues.jboss.org/browse/ARQ-1718 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Reporter: Tadeas Kriz > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Beta1 > > > There should be a way to simply test on device, without the need to use serial id, if only one device is connected. Adb has this functionality (if only one device (real or emulated) is connected, it uses it, or with -d switch to use real device (-e for emulated one)). Droidium should also allow this and quit with error if no serial id is specified, but more devices are connected. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 14:07:24 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 26 Jun 2014 14:07:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-446) Add support for Groovy page objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-446: ------------------------------ Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/115 Applied patch as pull request: https://github.com/arquillian/arquillian-graphene/pull/115 > Add support for Groovy page objects > ----------------------------------- > > Key: ARQGRA-446 > URL: https://issues.jboss.org/browse/ARQGRA-446 > Project: Arquillian Graphene > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: configuration, core > Affects Versions: 2.0.2.Final > Reporter: Chris Jones > Attachments: graphene-groovy-test.zip, groovy-page-support (fixed paths).patch, groovy-page-support.patch > > > Page objects written in groovy throw a StackOverflowError. There seems to be a recursive issue when proxying groovy's metaclass property. > {code:title=GoogleGroovy.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.graphene.page.Location > import org.openqa.selenium.WebElement > import org.openqa.selenium.support.FindBy > @Location("https://www.google.com/") > public class GoogleGroovy { > @FindBy > WebElement q > def search(String query){ > q.sendKeys(query) > sleep(5000) > } > } > {code} > {code:title=GoogleJava.java|borderStyle=solid} > package test; > import org.jboss.arquillian.graphene.page.Location; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @Location("https://www.google.com/") > public class GoogleJava { > @FindBy > WebElement q; > public void search(String query) throws Exception { > q.sendKeys(query); > Thread.sleep(5000); > } > } > {code} > {code:title=GoogleTestCase.groovy|borderStyle=solid} > package test > import org.jboss.arquillian.drone.api.annotation.Drone > import org.jboss.arquillian.graphene.Graphene > import org.jboss.arquillian.junit.Arquillian > import org.junit.Test > import org.junit.runner.RunWith > import org.openqa.selenium.firefox.FirefoxDriver > @RunWith(Arquillian.class) > class GoogleTestCase { > @Drone > FirefoxDriver driver > @Test > def void testUsingJava(){ > def googleJava = Graphene.goTo(GoogleJava) > googleJava.search("hello world") > } > @Test > def void testUsingGroovy(){ > def googleGroovy = Graphene.goTo(GoogleGroovy) > googleGroovy.search("jello world") > } > } > {code} > {code:title=Stacktrace|borderStyle=solid} > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:08 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597979243' found in test.GoogleTestCase. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__$stMC' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Public field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > Jun 01, 2014 12:47:12 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field '__timeStamp__239_neverHappen1401597978002' found in test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8. Direct access to fields outside of the declaring class is not allowed. > java.lang.StackOverflowError > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at test.GoogleGroovy$$EnhancerByGraphene$$2eb2d5f8.getMetaClass() > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.checkCall(PogoMetaClassSite.java:59) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:36) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) > ..... > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 16:51:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 16:51:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1107) Provide means for using Spring configured data sources through Persistence Extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1107: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done https://github.com/arquillian/arquillian-extension-spring/commit/baafbe2ec8dd3f751decdb02411bd4b268113175 https://github.com/arquillian/arquillian-extension-spring/commit/77380810838c2a755bac63a8fc273696f22fd770 > Provide means for using Spring configured data sources through Persistence Extension > ------------------------------------------------------------------------------------ > > Key: ARQ-1107 > URL: https://issues.jboss.org/browse/ARQ-1107 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spring > Affects Versions: spring_1.0.0.Beta1 > Reporter: Jakub Narloch > Assignee: Jakub Narloch > Fix For: spring_1.0.0.next > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 16:53:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 16:53:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1806) Disable failing Spring test due to unintended transactions behavior In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1806: ------------------------------- Fix Version/s: spring_1.0.0.Beta3 (was: spring_1.0.0.next) > Disable failing Spring test due to unintended transactions behavior > ------------------------------------------------------------------- > > Key: ARQ-1806 > URL: https://issues.jboss.org/browse/ARQ-1806 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Spring > Affects Versions: spring_1.0.0.Beta2 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: spring_1.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 16:53:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 16:53:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1107) Provide means for using Spring configured data sources through Persistence Extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1107: ------------------------------- Fix Version/s: spring_1.0.0.Beta3 (was: spring_1.0.0.next) > Provide means for using Spring configured data sources through Persistence Extension > ------------------------------------------------------------------------------------ > > Key: ARQ-1107 > URL: https://issues.jboss.org/browse/ARQ-1107 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spring > Affects Versions: spring_1.0.0.Beta1 > Reporter: Jakub Narloch > Assignee: Jakub Narloch > Fix For: spring_1.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 16:53:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 16:53:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1107) Provide means for using Spring configured data sources through Persistence Extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979774#comment-12979774 ] Aslak Knutsen edited comment on ARQ-1107 at 6/26/14 4:52 PM: ------------------------------------------------------------- pushed upstream https://github.com/arquillian/arquillian-extension-spring/commit/baafbe2ec8dd3f751decdb02411bd4b268113175 https://github.com/arquillian/arquillian-extension-spring/commit/77380810838c2a755bac63a8fc273696f22fd770 was (Author: aslak): https://github.com/arquillian/arquillian-extension-spring/commit/baafbe2ec8dd3f751decdb02411bd4b268113175 https://github.com/arquillian/arquillian-extension-spring/commit/77380810838c2a755bac63a8fc273696f22fd770 > Provide means for using Spring configured data sources through Persistence Extension > ------------------------------------------------------------------------------------ > > Key: ARQ-1107 > URL: https://issues.jboss.org/browse/ARQ-1107 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spring > Affects Versions: spring_1.0.0.Beta1 > Reporter: Jakub Narloch > Assignee: Jakub Narloch > Fix For: spring_1.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 16:55:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 16:55:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1107) Provide means for using Spring configured data sources through Persistence Extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1107. ------------------------------ > Provide means for using Spring configured data sources through Persistence Extension > ------------------------------------------------------------------------------------ > > Key: ARQ-1107 > URL: https://issues.jboss.org/browse/ARQ-1107 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spring > Affects Versions: spring_1.0.0.Beta1 > Reporter: Jakub Narloch > Assignee: Jakub Narloch > Fix For: spring_1.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 16:55:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 16:55:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1806) Disable failing Spring test due to unintended transactions behavior In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1806. ------------------------------ > Disable failing Spring test due to unintended transactions behavior > ------------------------------------------------------------------- > > Key: ARQ-1806 > URL: https://issues.jboss.org/browse/ARQ-1806 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Spring > Affects Versions: spring_1.0.0.Beta2 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: spring_1.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 16:57:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 16:57:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1402) Upgrade ShrinkWrap Resolvers to 2.0.0 Beta In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1402: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: spring_1.0.0.Beta3 Resolution: Done upstream https://github.com/arquillian/arquillian-extension-spring/commit/e86ed1bcfc80a144c994069a2d5e3d9373d32e3a > Upgrade ShrinkWrap Resolvers to 2.0.0 Beta > ------------------------------------------ > > Key: ARQ-1402 > URL: https://issues.jboss.org/browse/ARQ-1402 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spring > Affects Versions: spring_1.0.0.next > Reporter: Jakub Narloch > Assignee: Jakub Narloch > Fix For: spring_1.0.0.Beta3 > > > Upgrade the ShrinkWrap resolvers to newest version. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 16:57:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 16:57:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1402) Upgrade ShrinkWrap Resolvers to 2.0.0 Beta In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1402. ------------------------------ > Upgrade ShrinkWrap Resolvers to 2.0.0 Beta > ------------------------------------------ > > Key: ARQ-1402 > URL: https://issues.jboss.org/browse/ARQ-1402 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spring > Affects Versions: spring_1.0.0.next > Reporter: Jakub Narloch > Assignee: Jakub Narloch > Fix For: spring_1.0.0.Beta3 > > > Upgrade the ShrinkWrap resolvers to newest version. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 18:41:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 18:41:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1807) Exceptions in JUnit After will mask exceptions that happen in Before/Test In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1807: ---------------------------------- Summary: Exceptions in JUnit After will mask exceptions that happen in Before/Test Key: ARQ-1807 URL: https://issues.jboss.org/browse/ARQ-1807 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Harness Integration Affects Versions: 1.1.5.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 2.0.0.Beta1 Exceptions in the After phase will override exceptions that happened in Before and Test. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 18:45:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 18:45:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1808) The original cause of Exception in container is lost if exception is of type InvocationTargetException In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1808: ---------------------------------- Summary: The original cause of Exception in container is lost if exception is of type InvocationTargetException Key: ARQ-1808 URL: https://issues.jboss.org/browse/ARQ-1808 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.5.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen As oppose to most other Exceptions, InvocationTargetException does not use the cause field as the cause of the InvocationTargetException, rather it uses target. When the ExceptionProxy recreates the Exceptions from the container side on the client side, the actual cause of the InvocationTargetException is lost. The only cause you get is something like: Could not create ManagerImpl. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 18:51:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 18:51:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1807) Exceptions in JUnit After will mask exceptions that happen in Before/Test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1807: ------------------------------- Fix Version/s: 1.1.6.Final (was: 2.0.0.Beta1) > Exceptions in JUnit After will mask exceptions that happen in Before/Test > ------------------------------------------------------------------------- > > Key: ARQ-1807 > URL: https://issues.jboss.org/browse/ARQ-1807 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Harness Integration > Affects Versions: 1.1.5.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.6.Final > > > Exceptions in the After phase will override exceptions that happened in Before and Test. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 18:51:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 18:51:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1808) The original cause of Exception in container is lost if exception is of type InvocationTargetException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1808. -------------------------------- Fix Version/s: 1.1.6.Final Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/4b388320fadee67e8630004628f6f3a9aa8d27b7 > The original cause of Exception in container is lost if exception is of type InvocationTargetException > ------------------------------------------------------------------------------------------------------ > > Key: ARQ-1808 > URL: https://issues.jboss.org/browse/ARQ-1808 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.5.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.6.Final > > > As oppose to most other Exceptions, InvocationTargetException does not use the cause field as the cause of the InvocationTargetException, rather it uses target. > When the ExceptionProxy recreates the Exceptions from the container side on the client side, the actual cause of the InvocationTargetException is lost. > The only cause you get is something like: Could not create ManagerImpl. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 18:51:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Thu, 26 Jun 2014 18:51:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1807) Exceptions in JUnit After will mask exceptions that happen in Before/Test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1807. -------------------------------- Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/628eb78b35f06a78e9d5a2f47f8773d3f4409c00 > Exceptions in JUnit After will mask exceptions that happen in Before/Test > ------------------------------------------------------------------------- > > Key: ARQ-1807 > URL: https://issues.jboss.org/browse/ARQ-1807 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Harness Integration > Affects Versions: 1.1.5.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.6.Final > > > Exceptions in the After phase will override exceptions that happened in Before and Test. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 10:25:24 2014 From: issues at jboss.org (Steven Dodd (JIRA)) Date: Fri, 27 Jun 2014 10:25:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1809) @ShouldMatchDataSet is broken when ordering by non-string columns In-Reply-To: References: Message-ID: Steven Dodd created ARQ-1809: -------------------------------- Summary: @ShouldMatchDataSet is broken when ordering by non-string columns Key: ARQ-1809 URL: https://issues.jboss.org/browse/ARQ-1809 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha7 Reporter: Steven Dodd Assignee: Bartosz Majsak Steps to reproduce: 1. Create a table, "test", with a single column, an integer primary key, "id". 2. Try the following test case under the persistence extension: {code} @UsingDataSet({test.yml}) @ShouldMatchDataSet(value={test.yml}) @Test public void test() { // do nothing } {code} {code:title=test.yml} test: - id: -1 - id: -2 {code} Result: test fails. Reason: The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. The actual dataset is loaded by , and has all of its column types set to their actual types in the database. DataSetComparator wraps each dataset in a SortedTable, to provide a consistent ordering for comparison. SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. As a result, the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. Suggested Fix: The expected dataset needs to have accurate column types assigned, not UNKNOWN. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 10:27:24 2014 From: issues at jboss.org (Steven Dodd (JIRA)) Date: Fri, 27 Jun 2014 10:27:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1809) @ShouldMatchDataSet is broken when ordering by non-string columns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Dodd updated ARQ-1809: ----------------------------- Description: Steps to reproduce: 1. Create a table, "test", with a single column, an integer primary key, "id". 2. Try the following test case under the persistence extension: {code} @UsingDataSet({test.yml}) @ShouldMatchDataSet(value={test.yml}) @Test public void test() { // do nothing } {code} {code:title=test.yml} test: - id: -1 - id: -2 {code} Result: test fails like so: {code} java.lang.AssertionError: Test failed in 4 cases. test | In row 0: expected value of id "-1" but was "-2". test | In row 0: expected value of owner_id "-1" but was "-2". test | In row 1: expected value of id "-2" but was "-1". test | In row 1: expected value of owner_id "-2" but was "-1". {code} Reason: The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. The actual dataset is loaded by , and has all of its column types set to their actual types in the database. DataSetComparator wraps each dataset in a SortedTable, to provide a consistent ordering for comparison. SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. As a result, the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. Suggested Fix: The expected dataset needs to have accurate column types assigned, not UNKNOWN. was: Steps to reproduce: 1. Create a table, "test", with a single column, an integer primary key, "id". 2. Try the following test case under the persistence extension: {code} @UsingDataSet({test.yml}) @ShouldMatchDataSet(value={test.yml}) @Test public void test() { // do nothing } {code} {code:title=test.yml} test: - id: -1 - id: -2 {code} Result: test fails. Reason: The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. The actual dataset is loaded by , and has all of its column types set to their actual types in the database. DataSetComparator wraps each dataset in a SortedTable, to provide a consistent ordering for comparison. SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. As a result, the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. Suggested Fix: The expected dataset needs to have accurate column types assigned, not UNKNOWN. > @ShouldMatchDataSet is broken when ordering by non-string columns > ----------------------------------------------------------------- > > Key: ARQ-1809 > URL: https://issues.jboss.org/browse/ARQ-1809 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Steven Dodd > Assignee: Bartosz Majsak > > Steps to reproduce: > 1. Create a table, "test", with a single column, an integer primary key, "id". > 2. Try the following test case under the persistence extension: > {code} > @UsingDataSet({test.yml}) > @ShouldMatchDataSet(value={test.yml}) > @Test > public void test() { > // do nothing > } > {code} > {code:title=test.yml} > test: > - id: -1 > - id: -2 > {code} > Result: test fails like so: > {code} > java.lang.AssertionError: Test failed in 4 cases. > test | In row 0: expected value of id "-1" but was "-2". > test | In row 0: expected value of owner_id "-1" but was "-2". > test | In row 1: expected value of id "-2" but was "-1". > test | In row 1: expected value of owner_id "-2" but was "-1". > {code} > Reason: > The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. > The actual dataset is loaded by , and has all of its column types set to their actual types in the database. > DataSetComparator wraps each dataset in a SortedTable, to provide a consistent ordering for comparison. > SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. > As a result, the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. > Suggested Fix: > The expected dataset needs to have accurate column types assigned, not UNKNOWN. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 10:35:31 2014 From: issues at jboss.org (Steven Dodd (JIRA)) Date: Fri, 27 Jun 2014 10:35:31 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1809) @ShouldMatchDataSet is broken when ordering by non-string columns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Dodd updated ARQ-1809: ----------------------------- Description: Steps to reproduce: 1. Create a table, "test", with a single column, an integer primary key, "id". 2. Try the following test case under the persistence extension: {code} @UsingDataSet({test.yml}) @ShouldMatchDataSet(value={test.yml}) @Test public void test() { // do nothing } {code} {code:title=test.yml} test: - id: -1 - id: -2 {code} Result: test fails like so: {code} java.lang.AssertionError: Test failed in 4 cases. test | In row 0: expected value of id "-1" but was "-2". test | In row 0: expected value of owner_id "-1" but was "-2". test | In row 1: expected value of id "-2" but was "-1". test | In row 1: expected value of owner_id "-2" but was "-1". {code} Reason: The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. The actual dataset is loaded by , and has all of its column types set to their actual types in the database. DataSetComparator wraps each dataset in a SortedTable, to provide a consistent row ordering for comparison. SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. As a result, the rows of the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. Suggested Fix: The expected dataset needs to have accurate column types assigned, not UNKNOWN. was: Steps to reproduce: 1. Create a table, "test", with a single column, an integer primary key, "id". 2. Try the following test case under the persistence extension: {code} @UsingDataSet({test.yml}) @ShouldMatchDataSet(value={test.yml}) @Test public void test() { // do nothing } {code} {code:title=test.yml} test: - id: -1 - id: -2 {code} Result: test fails like so: {code} java.lang.AssertionError: Test failed in 4 cases. test | In row 0: expected value of id "-1" but was "-2". test | In row 0: expected value of owner_id "-1" but was "-2". test | In row 1: expected value of id "-2" but was "-1". test | In row 1: expected value of owner_id "-2" but was "-1". {code} Reason: The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. The actual dataset is loaded by , and has all of its column types set to their actual types in the database. DataSetComparator wraps each dataset in a SortedTable, to provide a consistent ordering for comparison. SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. As a result, the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. Suggested Fix: The expected dataset needs to have accurate column types assigned, not UNKNOWN. > @ShouldMatchDataSet is broken when ordering by non-string columns > ----------------------------------------------------------------- > > Key: ARQ-1809 > URL: https://issues.jboss.org/browse/ARQ-1809 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Steven Dodd > Assignee: Bartosz Majsak > > Steps to reproduce: > 1. Create a table, "test", with a single column, an integer primary key, "id". > 2. Try the following test case under the persistence extension: > {code} > @UsingDataSet({test.yml}) > @ShouldMatchDataSet(value={test.yml}) > @Test > public void test() { > // do nothing > } > {code} > {code:title=test.yml} > test: > - id: -1 > - id: -2 > {code} > Result: test fails like so: > {code} > java.lang.AssertionError: Test failed in 4 cases. > test | In row 0: expected value of id "-1" but was "-2". > test | In row 0: expected value of owner_id "-1" but was "-2". > test | In row 1: expected value of id "-2" but was "-1". > test | In row 1: expected value of owner_id "-2" but was "-1". > {code} > Reason: > The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. > The actual dataset is loaded by , and has all of its column types set to their actual types in the database. > DataSetComparator wraps each dataset in a SortedTable, to provide a consistent row ordering for comparison. > SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. > As a result, the rows of the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. > Suggested Fix: > The expected dataset needs to have accurate column types assigned, not UNKNOWN. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 10:57:24 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 27 Jun 2014 10:57:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1809) @ShouldMatchDataSet is broken when ordering by non-string columns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1809: -------------------------------- Fix Version/s: persistence_1.0.0.next > @ShouldMatchDataSet is broken when ordering by non-string columns > ----------------------------------------------------------------- > > Key: ARQ-1809 > URL: https://issues.jboss.org/browse/ARQ-1809 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Steven Dodd > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Steps to reproduce: > 1. Create a table, "test", with a single column, an integer primary key, "id". > 2. Try the following test case under the persistence extension: > {code} > @UsingDataSet({test.yml}) > @ShouldMatchDataSet(value={test.yml}) > @Test > public void test() { > // do nothing > } > {code} > {code:title=test.yml} > test: > - id: -1 > - id: -2 > {code} > Result: test fails like so: > {code} > java.lang.AssertionError: Test failed in 4 cases. > test | In row 0: expected value of id "-1" but was "-2". > test | In row 0: expected value of owner_id "-1" but was "-2". > test | In row 1: expected value of id "-2" but was "-1". > test | In row 1: expected value of owner_id "-2" but was "-1". > {code} > Reason: > The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. > The actual dataset is loaded by , and has all of its column types set to their actual types in the database. > DataSetComparator wraps each dataset in a SortedTable, to provide a consistent row ordering for comparison. > SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. > As a result, the rows of the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. > Suggested Fix: > The expected dataset needs to have accurate column types assigned, not UNKNOWN. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 11:01:31 2014 From: issues at jboss.org (Steven Dodd (JIRA)) Date: Fri, 27 Jun 2014 11:01:31 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1809) @ShouldMatchDataSet is broken when ordering by non-string columns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Dodd updated ARQ-1809: ----------------------------- Description: Steps to reproduce: 1. Create a table, "test", with a single column, an integer primary key, "id". 2. Try the following test case under the persistence extension: {code} @UsingDataSet({test.yml}) @ShouldMatchDataSet(value={test.yml}) @Test public void test() { // do nothing } {code} {code:title=test.yml} test: - id: -1 - id: -2 {code} Result: test fails like so: {code} java.lang.AssertionError: Test failed in 4 cases. test | In row 0: expected value of id "-1" but was "-2". test | In row 1: expected value of id "-2" but was "-1". {code} Reason: The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. The actual dataset is loaded by , and has all of its column types set to their actual types in the database. DataSetComparator wraps each dataset in a SortedTable, to provide a consistent row ordering for comparison. SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. As a result, the rows of the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. Suggested Fix: The expected dataset needs to have accurate column types assigned, not UNKNOWN. was: Steps to reproduce: 1. Create a table, "test", with a single column, an integer primary key, "id". 2. Try the following test case under the persistence extension: {code} @UsingDataSet({test.yml}) @ShouldMatchDataSet(value={test.yml}) @Test public void test() { // do nothing } {code} {code:title=test.yml} test: - id: -1 - id: -2 {code} Result: test fails like so: {code} java.lang.AssertionError: Test failed in 4 cases. test | In row 0: expected value of id "-1" but was "-2". test | In row 0: expected value of owner_id "-1" but was "-2". test | In row 1: expected value of id "-2" but was "-1". test | In row 1: expected value of owner_id "-2" but was "-1". {code} Reason: The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. The actual dataset is loaded by , and has all of its column types set to their actual types in the database. DataSetComparator wraps each dataset in a SortedTable, to provide a consistent row ordering for comparison. SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. As a result, the rows of the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. Suggested Fix: The expected dataset needs to have accurate column types assigned, not UNKNOWN. > @ShouldMatchDataSet is broken when ordering by non-string columns > ----------------------------------------------------------------- > > Key: ARQ-1809 > URL: https://issues.jboss.org/browse/ARQ-1809 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Steven Dodd > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Steps to reproduce: > 1. Create a table, "test", with a single column, an integer primary key, "id". > 2. Try the following test case under the persistence extension: > {code} > @UsingDataSet({test.yml}) > @ShouldMatchDataSet(value={test.yml}) > @Test > public void test() { > // do nothing > } > {code} > {code:title=test.yml} > test: > - id: -1 > - id: -2 > {code} > Result: test fails like so: > {code} > java.lang.AssertionError: Test failed in 4 cases. > test | In row 0: expected value of id "-1" but was "-2". > test | In row 1: expected value of id "-2" but was "-1". > {code} > Reason: > The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. > The actual dataset is loaded by , and has all of its column types set to their actual types in the database. > DataSetComparator wraps each dataset in a SortedTable, to provide a consistent row ordering for comparison. > SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. > As a result, the rows of the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. > Suggested Fix: > The expected dataset needs to have accurate column types assigned, not UNKNOWN. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 11:01:32 2014 From: issues at jboss.org (Steven Dodd (JIRA)) Date: Fri, 27 Jun 2014 11:01:32 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1809) @ShouldMatchDataSet is broken when ordering by non-string columns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Dodd updated ARQ-1809: ----------------------------- Description: Steps to reproduce: 1. Create a table, "test", with a single column, an integer primary key, "id". 2. Try the following test case under the persistence extension: {code} @UsingDataSet({test.yml}) @ShouldMatchDataSet(value={test.yml}) @Test public void test() { // do nothing } {code} {code:title=test.yml} test: - id: -1 - id: -2 {code} Result: test fails like so: {code} java.lang.AssertionError: Test failed in 2 cases. test | In row 0: expected value of id "-1" but was "-2". test | In row 1: expected value of id "-2" but was "-1". {code} Reason: The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. The actual dataset is loaded by , and has all of its column types set to their actual types in the database. DataSetComparator wraps each dataset in a SortedTable, to provide a consistent row ordering for comparison. SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. As a result, the rows of the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. Suggested Fix: The expected dataset needs to have accurate column types assigned, not UNKNOWN. was: Steps to reproduce: 1. Create a table, "test", with a single column, an integer primary key, "id". 2. Try the following test case under the persistence extension: {code} @UsingDataSet({test.yml}) @ShouldMatchDataSet(value={test.yml}) @Test public void test() { // do nothing } {code} {code:title=test.yml} test: - id: -1 - id: -2 {code} Result: test fails like so: {code} java.lang.AssertionError: Test failed in 4 cases. test | In row 0: expected value of id "-1" but was "-2". test | In row 1: expected value of id "-2" but was "-1". {code} Reason: The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. The actual dataset is loaded by , and has all of its column types set to their actual types in the database. DataSetComparator wraps each dataset in a SortedTable, to provide a consistent row ordering for comparison. SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. As a result, the rows of the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. Suggested Fix: The expected dataset needs to have accurate column types assigned, not UNKNOWN. > @ShouldMatchDataSet is broken when ordering by non-string columns > ----------------------------------------------------------------- > > Key: ARQ-1809 > URL: https://issues.jboss.org/browse/ARQ-1809 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Steven Dodd > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Steps to reproduce: > 1. Create a table, "test", with a single column, an integer primary key, "id". > 2. Try the following test case under the persistence extension: > {code} > @UsingDataSet({test.yml}) > @ShouldMatchDataSet(value={test.yml}) > @Test > public void test() { > // do nothing > } > {code} > {code:title=test.yml} > test: > - id: -1 > - id: -2 > {code} > Result: test fails like so: > {code} > java.lang.AssertionError: Test failed in 2 cases. > test | In row 0: expected value of id "-1" but was "-2". > test | In row 1: expected value of id "-2" but was "-1". > {code} > Reason: > The expected dataset is loaded by the YamlDataSetProducer, and has all of its column types set to UNKNOWN. > The actual dataset is loaded by , and has all of its column types set to their actual types in the database. > DataSetComparator wraps each dataset in a SortedTable, to provide a consistent row ordering for comparison. > SortedTable ends up sorting every column of the expected dataset as strings, because the column types are UNKNOWN, but it sorts the actual dataset columns using their actual column types, e.g. numeric sort in the test case above. > As a result, the rows of the expected and actual datasets are not consistently sorted for comparison, which results in totally inaccurate comparison results. > Suggested Fix: > The expected dataset needs to have accurate column types assigned, not UNKNOWN. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 11:05:25 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 27 Jun 2014 11:05:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1782) @UsingDataSet/@ShouldMatchDataSet always makes test succeed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1782: -------------------------------- Fix Version/s: persistence_1.0.0.next > @UsingDataSet/@ShouldMatchDataSet always makes test succeed > ----------------------------------------------------------- > > Key: ARQ-1782 > URL: https://issues.jboss.org/browse/ARQ-1782 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Environment: WildFly 8 CR 2 > Reporter: Nicklas Karlsson > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > {code:xml} > > xsi:schemaLocation=" > http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd"> > 4.0.0 > fi.affecto.marela > arq-concept > 1.0.0-SNAPSHOT > jar > > UTF-8 > chrome > > > > > org.jboss.arquillian > arquillian-bom > 1.1.4.Final > import > pom > > > org.jboss.arquillian.extension > arquillian-drone-bom > 1.3.0.Final > pom > import > > > org.jboss.arquillian.selenium > selenium-bom > 2.41.0 > pom > import > > > > > > junit > junit > 4.11 > test > > > org.jboss.arquillian.junit > arquillian-junit-container > test > > > org.hibernate > hibernate-jpamodelgen > 4.3.5.Final > provided > > > org.jboss.arquillian.graphene > graphene-webdriver > 2.0.2.Final > pom > test > > > org.jboss.arquillian.extension > arquillian-persistence-core > 1.0.0.Alpha7 > > > org.jboss.arquillian.extension > arquillian-persistence-dbunit > 1.0.0.Alpha7 > > > > > arq-wildfly > > > org.jboss.spec > jboss-javaee-7.0 > 1.0.0.Final > pom > provided > > > org.wildfly > wildfly-arquillian-container-remote > 8.1.0.CR2 > test > > > org.jboss.arquillian.protocol > arquillian-protocol-servlet > test > > > > > > > > maven-compiler-plugin > 2.3.2 > > 1.7 > 1.7 > > > > > > src/test/resources > true > > > > > {code} > {code:java} > package fi.affecto.marela.test; > import javax.inject.Inject; > import javax.persistence.EntityManager; > import javax.persistence.PersistenceContext; > import javax.transaction.UserTransaction; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.arquillian.persistence.ShouldMatchDataSet; > import org.jboss.arquillian.persistence.UsingDataSet; > import org.jboss.arquillian.transaction.api.annotation.Transactional; > import org.jboss.shrinkwrap.api.Archive; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.WebArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > import fi.affecto.marela.jpa.Game; > @RunWith(Arquillian.class) > public class PersistenceExtensionTest > { > @Deployment > public static Archive createDeployment() > { > return ShrinkWrap.create(WebArchive.class, "test.war").addPackage(Game.class.getPackage()) > .addAsResource("persistence.xml", "META-INF/persistence.xml") > .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); > } > @PersistenceContext > EntityManager em; > @Inject > UserTransaction utx; > @Test > public void testA() throws Exception > { > Assert.assertNotNull(em); > utx.begin(); > // em.joinTransaction(); > Game g = new Game(); > g.setId(666L); > g.setTitle("x"); > Assert.assertFalse(em.contains(g)); > g = em.merge(g); > Assert.assertTrue(em.contains(g)); > utx.rollback(); > } > > @Test > @Transactional > public void testB() throws Exception > { > Assert.assertNotNull(em); > Game g = new Game(); > g.setId(666L); > g.setTitle("x"); > Assert.assertFalse(em.contains(g)); > g = em.merge(g); > Assert.assertTrue(em.contains(g)); > } > @Test > // @UsingDataSet("games.yml") > // @ShouldMatchDataSet("games-check.yml") > @Transactional > public void testC() throws Exception > { > Assert.assertTrue(false); > } > } > {code} > testC succeeds if the annotations are uncommented. > Furthermore, there is something strange with the em/transactions, the persistence works even if the em doesn't join the transaction and the em complains of a detached instance if merge() is switched for persist() -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 11:07:26 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 27 Jun 2014 11:07:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1645) persistence doesn't support multiple datasources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1645: -------------------------------- Fix Version/s: persistence_1.0.0.next > persistence doesn't support multiple datasources > ------------------------------------------------ > > Key: ARQ-1645 > URL: https://issues.jboss.org/browse/ARQ-1645 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Romain Manni-Bucau > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > It is common to use multiple datsources (in fact all apps I'm working with does it) and ATM dbunit extension doesn't support multiple datsource init/asserts (UsingDataSet and ExpectedDataSet). > Would be great to get a plural version of @DataSource and @XDataSet -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 11:07:26 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 27 Jun 2014 11:07:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1644) Arquillian Persistence doesn't work with embedded/Local containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1644: -------------------------------- Fix Version/s: persistence_1.0.0.next > Arquillian Persistence doesn't work with embedded/Local containers > ------------------------------------------------------------------ > > Key: ARQ-1644 > URL: https://issues.jboss.org/browse/ARQ-1644 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Romain Manni-Bucau > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Because of the way its Extensions are written arquillien-extension-persistence doesn't work with Local containers (tested with OpenEJB, need hack like [the one mentiong in the blog|http://rmannibucau.wordpress.com/2013/09/05/arquillian-persistence-and-embedded-container-openejbdbunithsqldb-case/]) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 11:07:26 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 27 Jun 2014 11:07:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1337) Should support multiple datasources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1337: -------------------------------- Fix Version/s: persistence_1.0.0.next > Should support multiple datasources > ----------------------------------- > > Key: ARQ-1337 > URL: https://issues.jboss.org/browse/ARQ-1337 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Seeding, comparing and applying scripts should be possible for multiple datasources. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 11:09:25 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 27 Jun 2014 11:09:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1332) Should be able to script data in the data sets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1332: -------------------------------- Fix Version/s: persistence_1.0.0.next > Should be able to script data in the data sets > ---------------------------------------------- > > Key: ARQ-1332 > URL: https://issues.jboss.org/browse/ARQ-1332 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > The DataSet represents a collection of tables (rows) used to seed the database. However it's static nature is not sufficient in many cases. Imagine testing time sensitive data. It could be really handy to have possibility of defining date as "three days from today" or having current time by simply invoking "now()" function. With the power of a scripting language at your disposal it should be achieved very easy. > > The goal of this project is to extend the Arquillian Persistence Extension usage of DBUnit and introduce the concept ScriptableDataSet. By leveraging "Scripting for the Java Platform" (JSR 223) introduced in JDK 6 we can use plethora of languages to add dynamic flavor to our data driven tests. > Supporting a script location (and perhaps even a function in that script file) might be a nice addition as well. That externalizes the code and allows for reuse. > As a starting point groovy can be considered. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 12:18:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 12:18:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1810) Update Tomcat Containers test suite to ShrinWrap Resolver 2.0 In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1810: ---------------------------------- Summary: Update Tomcat Containers test suite to ShrinWrap Resolver 2.0 Key: ARQ-1810 URL: https://issues.jboss.org/browse/ARQ-1810 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR6 Reporter: Aslak Knutsen -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 12:20:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 12:20:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1810) Update Tomcat Containers test suite to ShrinWrap Resolver 2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1810. -------------------------------- Assignee: Aslak Knutsen Fix Version/s: tomcat_1.0.0.Final Resolution: Done pushed upstream https://github.com/arquillian/arquillian-container-tomcat/commit/c59dd9635dfdfdb4422e4861b4d21496e9ca875c > Update Tomcat Containers test suite to ShrinWrap Resolver 2.0 > ------------------------------------------------------------- > > Key: ARQ-1810 > URL: https://issues.jboss.org/browse/ARQ-1810 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 12:20:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 12:20:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1810) Update Tomcat Containers test suite to ShrinkWrap Resolver 2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1810: ------------------------------- Summary: Update Tomcat Containers test suite to ShrinkWrap Resolver 2.0 (was: Update Tomcat Containers test suite to ShrinWrap Resolver 2.0) > Update Tomcat Containers test suite to ShrinkWrap Resolver 2.0 > -------------------------------------------------------------- > > Key: ARQ-1810 > URL: https://issues.jboss.org/browse/ARQ-1810 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 12:30:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 12:30:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-865) Allow managerUrl (or manager contextPath) to be configured in remote 6 container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-865. ------------------------------- Labels: (was: starter) Assignee: Aslak Knutsen Fix Version/s: tomcat_1.0.0.CR5 Resolution: Out of Date We now have a separate Tomcat 7 Remote adapter > Allow managerUrl (or manager contextPath) to be configured in remote 6 container > -------------------------------------------------------------------------------- > > Key: ARQ-865 > URL: https://issues.jboss.org/browse/ARQ-865 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR3 > Reporter: Dan Allen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.CR5 > > > Tomcat 7 changed the context path for the manager apps. For the purpose of what the Arquillian adapter uses, the context path changed from /manager to /manager/text. > Unfortunately, the tomcat adapter does not provide a way to configure the context path of the manager url. It builds it automatically as follows: > {code} > protected URL createManagerUrl() throws MalformedURLException > { > final String template = "http://%s:%d/manager"; > return new URL(String.format(template, bindAddress, bindHttpPort)); > } > {code} > At a minimum, we should add a new property "managerContextPath" and honor that in this method. > Better would be to also allow the managerUrl to be overridden entirely. This currently does not work because > 1. arquillian cannot convert a configuration property to a URL > 2. even if it did, the value is overridden in the validate() method anyway > This fix will allow the Tomcat 6 remote adapter to work with Tomcat 7. > Side note: > The user should also be advised that it is necessary to include the JMX startup properties when starting Tomcat 7. > -Dcom.sun.management.jmxremote.port=8089 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 12:32:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 12:32:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-824) Verify Arquillian can run on JDK 1.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-824: ------------------------------ Component/s: (was: Tomcat Containers) > Verify Arquillian can run on JDK 1.5 > ------------------------------------ > > Key: ARQ-824 > URL: https://issues.jboss.org/browse/ARQ-824 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Seam2, JBoss AS Containers, Test Protocol SPIs and Implementation > Affects Versions: 1.0.0.CR7 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > > Setting compiler options target/source to 1.5 is not enough to verify that the code can actually run on JDK 1.5 since it ignores API changes. To avoid forcing developers to have JDK 1.5 installed to compile, we can add e.g. the Animal Sniffer Maven Plugin to verify using usage of JDK based on known api signatures. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 12:38:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 12:38:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1519) Cannot load configuration with tomcat-managed-1.0.0.CR5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1519. -------------------------------- Assignee: Aslak Knutsen Resolution: Out of Date Fixed indirectly by ARQ-1810 as the Adapters exposed versions now match closer to the Arquillian Core versions. The correct thing here would be to use the Arquillian-BOM to lock the Core expected versions and not let the Tomcat Adapter override the versions that Core depend on. > Cannot load configuration with tomcat-managed-1.0.0.CR5 > ------------------------------------------------------- > > Key: ARQ-1519 > URL: https://issues.jboss.org/browse/ARQ-1519 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > > {code} > java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor > at org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.fromStream(DescriptorImporterBase.java:155) > at org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.from(DescriptorImporterBase.java:182) > at org.jboss.arquillian.config.impl.extension.ConfigurationRegistrar.loadConfiguration(ConfigurationRegistrar.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.ManagerImpl.start(ManagerImpl.java:261) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.(EventTestRunnerAdaptor.java:56) > {code} > When debugging this I see > {code} > java.lang.NoSuchMethodError: org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.fromStream(Ljava/io/InputStream;Z)Lorg/jboss/shrinkwrap/descriptor/api/Descriptor;{code} > this is however never fed back to the client -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 12:38:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 12:38:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1519) Cannot load configuration with tomcat-managed-1.0.0.CR5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1519: ------------------------------- Fix Version/s: tomcat_1.0.0.Final > Cannot load configuration with tomcat-managed-1.0.0.CR5 > ------------------------------------------------------- > > Key: ARQ-1519 > URL: https://issues.jboss.org/browse/ARQ-1519 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > {code} > java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor > at org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.fromStream(DescriptorImporterBase.java:155) > at org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.from(DescriptorImporterBase.java:182) > at org.jboss.arquillian.config.impl.extension.ConfigurationRegistrar.loadConfiguration(ConfigurationRegistrar.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.ManagerImpl.start(ManagerImpl.java:261) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.(EventTestRunnerAdaptor.java:56) > {code} > When debugging this I see > {code} > java.lang.NoSuchMethodError: org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.fromStream(Ljava/io/InputStream;Z)Lorg/jboss/shrinkwrap/descriptor/api/Descriptor;{code} > this is however never fed back to the client -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 12:42:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 12:42:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1201) FileNotFound exception when trying to access static web resouces - tomcat-embedded-6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1201: ------------------------------- Fix Version/s: tomcat_1.0.0.Final > FileNotFound exception when trying to access static web resouces - tomcat-embedded-6 > ------------------------------------------------------------------------------------ > > Key: ARQ-1201 > URL: https://issues.jboss.org/browse/ARQ-1201 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR4 > Environment: Embedded > Reporter: George Vagenas > Labels: resources, static, tomcat-embedded-6,, webResources > Fix For: tomcat_1.0.0.Final > > Attachments: arquillian-container-tomcat-embedded-6.patch, SimpleArqTest_DefaultWebXML.tar.gz > > > When trying to access static web resource inside WAR, such as hello_world.txt: > WAR > |--WEB-INF/ > |--demo/ > |--hello_world.txt > A FileNotFoundException is fired. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 12:44:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 12:44:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-629) Tomcat6-managed container: running 39 testcase classes with n test methods each on hudson result in a crash on the 10th deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-629. ----------------------------- Assignee: Aslak Knutsen Resolution: Done Nothing to fix in the Adapter it self, closing. See issues linked/in comments. > Tomcat6-managed container: running 39 testcase classes with n test methods each on hudson result in a crash on the 10th deployment > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: ARQ-629 > URL: https://issues.jboss.org/browse/ARQ-629 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: 1.0.0.CR4 > Reporter: Geoffrey De Smet > Assignee: Aslak Knutsen > Priority: Minor > > So it deploys 39 times, and after about the 10th or so it crashes because of perm gen space IIRC. > My build was here, but on build 5 or so I switched it from tomcat to jboss7-managed: > https://hudson.qa.jboss.com/hudson/view/Drools%20jBPM/job/guvnor-ge0ffrey-seam3upgrade/ -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 12:52:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 12:52:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1777) Test hangs on remote Tomcat 6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980033#comment-12980033 ] Aslak Knutsen commented on ARQ-1777: ------------------------------------ Not sure I understand quite what's wrong / how its wrong here.. Could you provide a complete project that shows the error? I see from your configuration that you're using the Servlet 3.0 protocol on a Tomcat 6 server. Tomcat 6 only support Servlet 2.5. This would result in Tests not begin executed, but I would expect you see a error about not getting a response from the TestRunnerServlet or similar.. ? > Test hangs on remote Tomcat 6 > ----------------------------- > > Key: ARQ-1777 > URL: https://issues.jboss.org/browse/ARQ-1777 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Pramod Kankure > > I have observed that test hangs when executing on tomcat 6 remote container. > My arquillian.xml looks like below. ( I don't use authentication for jmx) > > xmlns="http://jboss.org/schema/arquillian" > xsi:schemaLocation="http://jboss.org/schema/arquillian > http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> > > > > > 1776 > localhost > 8090 > > > > > The test do stops with an error when the server is down or wrong HTTP port is specified. It does execute @deployment method of the test but never comes to execute the test method annoted with [~test.todd] -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 13:55:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 13:55:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1519) Cannot load configuration with tomcat-managed-1.0.0.CR5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1519. ------------------------------ > Cannot load configuration with tomcat-managed-1.0.0.CR5 > ------------------------------------------------------- > > Key: ARQ-1519 > URL: https://issues.jboss.org/browse/ARQ-1519 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > {code} > java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor > at org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.fromStream(DescriptorImporterBase.java:155) > at org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.from(DescriptorImporterBase.java:182) > at org.jboss.arquillian.config.impl.extension.ConfigurationRegistrar.loadConfiguration(ConfigurationRegistrar.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.ManagerImpl.start(ManagerImpl.java:261) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.(EventTestRunnerAdaptor.java:56) > {code} > When debugging this I see > {code} > java.lang.NoSuchMethodError: org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.fromStream(Ljava/io/InputStream;Z)Lorg/jboss/shrinkwrap/descriptor/api/Descriptor;{code} > this is however never fed back to the client -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 13:55:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 13:55:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1650) Managed container bypasses tomcat jul setup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1650. ------------------------------ > Managed container bypasses tomcat jul setup > ------------------------------------------- > > Key: ARQ-1650 > URL: https://issues.jboss.org/browse/ARQ-1650 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: tomcat_1.0.0.Final > > > This code from the catalina startup script is not done in the manged deployable container > {code} > # Set juli LogManager config file if it is present and an override has not been issued > if [ -z "$LOGGING_CONFIG" ]; then > if [ -r "$CATALINA_BASE"/conf/logging.properties ]; then > LOGGING_CONFIG="-Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties" > else > # Bugzilla 45585 > LOGGING_CONFIG="-Dnop" > fi > fi > if [ -z "$LOGGING_MANAGER" ]; then > LOGGING_MANAGER="-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" > fi > {code} > As a result, tomcat logging does not work -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 13:55:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 13:55:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1680) Tomcat 7 embedded adapter should be built against 7.0.52 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1680. ------------------------------ > Tomcat 7 embedded adapter should be built against 7.0.52 > -------------------------------------------------------- > > Key: ARQ-1680 > URL: https://issues.jboss.org/browse/ARQ-1680 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Environment: Tomcat 7.0.52, JDK 1.7 > Reporter: Tommy Tynj? > Assignee: Tommy Tynj? > Fix For: tomcat_1.0.0.Final > > > Tomcat 7 embedded container is built with a dependency on Tomcat 7.0.20, which was released 2011-08-11. The latest version of Tomcat is 7.0.52, and a lot of patches have been applied since 7.0.20 (see [changelog|http://tomcat.apache.org/tomcat-7.0-doc/changelog.html]). When relying on the 7.0.52 version of Tomcat 7 embedded in your project, it would be preferable to use an adapter that is built using that version, as in some (at least theoretical) corner cases, Arquillian could fail running tests in a 7.0.52 embedded container. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 13:55:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 13:55:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1799) Remove dependency on common-codecs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1799. ------------------------------ > Remove dependency on common-codecs > ---------------------------------- > > Key: ARQ-1799 > URL: https://issues.jboss.org/browse/ARQ-1799 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > Since client side can depend on Common-Codec and cause version conflicts with the Container, remove the external dependency and move Base64 encoding class internally. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 13:55:24 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 13:55:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1191) Tomcat Embedded 6 undeploy(archive) issue In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1191. ------------------------------ > Tomcat Embedded 6 undeploy(archive) issue > ----------------------------------------- > > Key: ARQ-1191 > URL: https://issues.jboss.org/browse/ARQ-1191 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR4 > Environment: Tomcat-embedded-6 > Reporter: George Vagenas > Assignee: Aslak Knutsen > Priority: Critical > Fix For: tomcat_1.0.0.Final > > Attachments: arquillian-container-tomcat.patch, SimpleArqTest.zip > > > Having two test classes that extend an abstract class that provides the deployment archive (actually the fact that they extend an abstract class is insignificant, the important point here is that the deployment archive name is the same). > When the test classes run individually pass the test. When these two test classes combined in a test suite, the first only pass and the second always fails. > @RunWith(Suite.class) > @SuiteClasses({ > RegisteredEchoServletTestCase.class, > RegisteredEchoServletTestCase2.class > }) > public class MyTestSuite { > } > Find attached @RunWith(Suite.class) > @SuiteClasses({ > RegisteredEchoServletTestCase.class, > RegisteredEchoServletTestCase2.class > }) > public class MyTestSuite { > } > Issue exists only on tomcat 6 container. I run the same test suite against tomcat-embedded-7 with success. > George -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 13:55:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 13:55:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-866) Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-866. ----------------------------- > Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > ------------------------------------------------------------------------------------------------- > > Key: ARQ-866 > URL: https://issues.jboss.org/browse/ARQ-866 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR3 > Reporter: Dan Allen > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.Final > > > The Tomcat managed container adapter assumes that catalina.base is the same as catalina.home. > {code} > String absolutePath = new File(CATALINA_HOME).getAbsolutePath(); > ... > cmd.add("-Dcatalina.base=" + absolutePath); > cmd.add("-Dcatalina.home=" + absolutePath); > {code} > However, this is not necessary true. For instance, when using Tomcat from Eclipse, the catalina.base (which includes the configuration files) is managed inside the Eclipse workspace. This allows the developer to modify Tomcat settings without affecting the system installation. > The fix for this problem is to add a configuration property named "catalinaBase" and honor if it's set when building the startup script. > This affects all the Tomcat managed containers (5, 6 and 7). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 13:55:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 13:55:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1810) Update Tomcat Containers test suite to ShrinkWrap Resolver 2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1810. ------------------------------ > Update Tomcat Containers test suite to ShrinkWrap Resolver 2.0 > -------------------------------------------------------------- > > Key: ARQ-1810 > URL: https://issues.jboss.org/browse/ARQ-1810 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 13:55:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 13:55:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-628) Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-628. ----------------------------- > Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency > ----------------------------------------------------------------------------------------------------- > > Key: ARQ-628 > URL: https://issues.jboss.org/browse/ARQ-628 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR2 > Environment: tomcat-managed-7 > application - richfaces-showcase-4.1.0-20111011-M3-tomcat6.war > Reporter: Juraj H?ska > Fix For: tomcat_1.0.0.Final > > > I have encountered this issue when I was testing richfaces-showcase application. It seems that tomcat-managed-7 has problem with applications which bring own weld-servlet dependency. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 13:55:25 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 13:55:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-701) Tomcat containers are not able to start after begin stop (AddressAlready in use) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-701. ----------------------------- > Tomcat containers are not able to start after begin stop (AddressAlready in use) > -------------------------------------------------------------------------------- > > Key: ARQ-701 > URL: https://issues.jboss.org/browse/ARQ-701 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR2 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > Setting a embedded Tomcat 7 container to manual control mode and calling, start/stop/start cause Address Already in use Exception. > stop should call tomcat.destroy > (possible other tomcat versions as well, investigate) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 14:01:26 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 27 Jun 2014 14:01:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-574) Tomcat managed should not require an installed tomcat server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-574. ----------------------------- Resolution: Won't Fix > Tomcat managed should not require an installed tomcat server > ------------------------------------------------------------ > > Key: ARQ-574 > URL: https://issues.jboss.org/browse/ARQ-574 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Geoffrey De Smet > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.CR7 > > > When starting up tomcat6-managed, the first SNAPSHOT, I get this: > {code} > Either CATALINA_HOME environment variable or catalinaHome property in Arquillian configuration must be set and point to a valid directory! null is not valid directory! > {code} > There are 2 problems with this: > - it's a maintenance hurdle, especially on hudson build slaves > - the build is not reproducible: the test results depends on the tomcat server version you've installed on your machine. > Solution: > Set the tomcat zip as a dependency (so it's in ~/.m2/repository) and unzip it to target and use that server installation. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 14:40:24 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Fri, 27 Jun 2014 14:40:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-1740 started by Alex Soto. > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Alex Soto > Priority: Minor > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 14:42:24 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Fri, 27 Jun 2014 14:42:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto reassigned ARQ-1740: ------------------------------ Assignee: Stefan Miklosovic (was: Alex Soto) I assign to you the issue so if you think that pull request is good you can close it. Of course if I have to close it, reassign again to me and I close it. > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 16:36:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 27 Jun 2014 16:36:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1740: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/arquillian/arquillian-recorder/pull/4 > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 27 16:36:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 27 Jun 2014 16:36:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1740: ----------------------------------- Assignee: Alex Soto (was: Stefan Miklosovic) > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Alex Soto > Priority: Minor > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 28 07:55:24 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Sat, 28 Jun 2014 07:55:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto reassigned ARQ-1740: ------------------------------ Assignee: Stefan Miklosovic (was: Alex Soto) Done!!! And sorry I haven't seen that there was a checkstyle to be run in Maven. PR here https://github.com/lordofthejars/arquillian-recorder/compare/arquillian:master...master > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 28 11:36:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 28 Jun 2014 11:36:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1740: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: recorder_1.0.0.Alpha4 Resolution: Done > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha4 > > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 28 11:40:36 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 28 Jun 2014 11:40:36 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reopened ARQ-1740: ------------------------------------ > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha4 > > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 28 11:40:40 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 28 Jun 2014 11:40:40 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1740. ------------------------------------ Resolution: Done > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha4 > > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 29 08:26:24 2014 From: issues at jboss.org (Juergen Zimmermann (JIRA)) Date: Sun, 29 Jun 2014 08:26:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: Juergen Zimmermann created ARQGRA-454: ----------------------------------------- Summary: NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final Key: ARQGRA-454 URL: https://issues.jboss.org/browse/ARQGRA-454 Project: Arquillian Graphene Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 2.0.3.Final Reporter: Juergen Zimmermann I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. The stacktrace: {code} org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: Error while initializing: class de.shop.util.IndexPage at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Caused by: java.lang.NullPointerException at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) ... 34 more {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 29 13:38:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 29 Jun 2014 13:38:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1735) Release Droidium 1.0.0.Alpha5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1735. ---------------------------------- > Release Droidium 1.0.0.Alpha5 > ----------------------------- > > Key: ARQ-1735 > URL: https://issues.jboss.org/browse/ARQ-1735 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 29 13:40:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 29 Jun 2014 13:40:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1581) Droidium does not work with remote emulators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1581. ---------------------------------- > Droidium does not work with remote emulators > -------------------------------------------- > > Key: ARQ-1581 > URL: https://issues.jboss.org/browse/ARQ-1581 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > *When*: > I use Android Jenkins Plugin to start the device > *Then*: > It starts the emulator using remote syntax, that is including --port port1,port2 > *Expect*: > Drodium will connect to already running emulator. > *Actual problem*: > AndroidDevice and IDevice isEmulator() call is not able to parse the data retrieved from adb devices. This results into Droidium trying to start emulator with the same name, however this emulator is already started so event marking correct startup is never send and test fails. > Output: > {code} > export ANDROID_ADB_SERVER_PORT=52892 > [tester at fedora19 ~]$ ANDROID_SDK_HOME=`pwd`/workspace/mobile-eap-test ./tools/android-sdk/platform-tools/adb devices > List of devices attached > localhost:46689 device > {code} > However, emulators are expected to be in format of emulator-XYZ. > Drodium should be able to modify the behavior to handle this correctly. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 29 13:50:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 29 Jun 2014 13:50:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-453) Support Apache HTTPD as a DeployableContainer in Managed mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-453: ------------------------------------- Assignee: Stefan Miklosovic > Support Apache HTTPD as a DeployableContainer in Managed mode > ------------------------------------------------------------- > > Key: ARQ-453 > URL: https://issues.jboss.org/browse/ARQ-453 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Apache HTTPD Containers > Reporter: Ondrej Zizka > Assignee: Stefan Miklosovic > Fix For: httpd_1.0.0.next > > > The DeployableContainer interface provided by Arquillian offer a simple abstraction over something that you can setup, start or stop. In addition it can support deploy and undeploy. > The same logic can be applied to pure services, e.g. Mail, Database or FTP servers. > The Apache HTTPD server adapter is a DeployableContainer implementation that control the lifecycle of a local Apache HTTP Server. The Adapter support adding additional HTTPD configuration during setup, and rely on calling out to the command line when starting and stopping the server. The Adapter work with both Windows and Linux based systems. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 29 16:01:25 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 29 Jun 2014 16:01:25 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-453) Support Apache HTTPD as a DeployableContainer in Managed mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-453: ---------------------------------- Assignee: (was: Stefan Miklosovic) > Support Apache HTTPD as a DeployableContainer in Managed mode > ------------------------------------------------------------- > > Key: ARQ-453 > URL: https://issues.jboss.org/browse/ARQ-453 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Apache HTTPD Containers > Reporter: Ondrej Zizka > Fix For: httpd_1.0.0.next > > > The DeployableContainer interface provided by Arquillian offer a simple abstraction over something that you can setup, start or stop. In addition it can support deploy and undeploy. > The same logic can be applied to pure services, e.g. Mail, Database or FTP servers. > The Apache HTTPD server adapter is a DeployableContainer implementation that control the lifecycle of a local Apache HTTP Server. The Adapter support adding additional HTTPD configuration during setup, and rely on calling out to the command line when starting and stopping the server. The Adapter work with both Windows and Linux based systems. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 29 16:01:26 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 29 Jun 2014 16:01:26 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-453) Support Apache HTTPD as a DeployableContainer in Managed mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980477#comment-12980477 ] Stefan Miklosovic commented on ARQ-453: --------------------------------------- [~ozizka] I am willing to code this adapter since with the existence of Arquillian Spacelift project it should be easy, however I do not know how to deal with these problems: 1) In case of managed container, this container has to exist prior to test execution so Apache server has to be installed somewhere in file system. When you take out-of-box installation of http server (e.g. in Fedora) you have to have root permissions to copy some files to /var/www. However, when you run a test, you do not have these write permissions. You would have to somehow manually tweak them before and it is just error prone approach. 2) In case you would take HTTP server with you in container adapter itself, you would have to compile it in advance with some prefix (1) but you do not know in advance how this prefix should look like. And you would have to potentially take into consideration various architectures when compiling (x86_64, i686 ... you name it) (1) https://httpd.apache.org/docs/2.4/install.html#configure > Support Apache HTTPD as a DeployableContainer in Managed mode > ------------------------------------------------------------- > > Key: ARQ-453 > URL: https://issues.jboss.org/browse/ARQ-453 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Apache HTTPD Containers > Reporter: Ondrej Zizka > Fix For: httpd_1.0.0.next > > > The DeployableContainer interface provided by Arquillian offer a simple abstraction over something that you can setup, start or stop. In addition it can support deploy and undeploy. > The same logic can be applied to pure services, e.g. Mail, Database or FTP servers. > The Apache HTTPD server adapter is a DeployableContainer implementation that control the lifecycle of a local Apache HTTP Server. The Adapter support adding additional HTTPD configuration during setup, and rely on calling out to the command line when starting and stopping the server. The Adapter work with both Windows and Linux based systems. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 29 19:11:24 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 29 Jun 2014 19:11:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-453) Support Apache HTTPD as a DeployableContainer in Managed mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980477#comment-12980477 ] Stefan Miklosovic edited comment on ARQ-453 at 6/29/14 7:09 PM: ---------------------------------------------------------------- [~ozizka] I am willing to code this adapter since with the existence of Arquillian Spacelift project it should be easy, however I do not know how to deal with these problems: 1) In case of managed container, this container has to exist prior to test execution so Apache server has to be installed somewhere in file system. When you take out-of-box installation of http server (e.g. in Fedora) you have to have root permissions to copy some files to /var/www. However, when you run a test, you do not have these write permissions. You would have to somehow manually tweak them before and it is just error prone approach. Starting and stopping of HTTPD server needs root as well. 2) In case you would take HTTP server with you in container adapter itself, you would have to compile it in advance with some prefix (1) but you do not know in advance how this prefix should look like. And you would have to potentially take into consideration various architectures when compiling (x86_64, i686 ... you name it) (1) https://httpd.apache.org/docs/2.4/install.html#configure was (Author: smikloso): [~ozizka] I am willing to code this adapter since with the existence of Arquillian Spacelift project it should be easy, however I do not know how to deal with these problems: 1) In case of managed container, this container has to exist prior to test execution so Apache server has to be installed somewhere in file system. When you take out-of-box installation of http server (e.g. in Fedora) you have to have root permissions to copy some files to /var/www. However, when you run a test, you do not have these write permissions. You would have to somehow manually tweak them before and it is just error prone approach. 2) In case you would take HTTP server with you in container adapter itself, you would have to compile it in advance with some prefix (1) but you do not know in advance how this prefix should look like. And you would have to potentially take into consideration various architectures when compiling (x86_64, i686 ... you name it) (1) https://httpd.apache.org/docs/2.4/install.html#configure > Support Apache HTTPD as a DeployableContainer in Managed mode > ------------------------------------------------------------- > > Key: ARQ-453 > URL: https://issues.jboss.org/browse/ARQ-453 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Apache HTTPD Containers > Reporter: Ondrej Zizka > Fix For: httpd_1.0.0.next > > > The DeployableContainer interface provided by Arquillian offer a simple abstraction over something that you can setup, start or stop. In addition it can support deploy and undeploy. > The same logic can be applied to pure services, e.g. Mail, Database or FTP servers. > The Apache HTTPD server adapter is a DeployableContainer implementation that control the lifecycle of a local Apache HTTP Server. The Adapter support adding additional HTTPD configuration during setup, and rely on calling out to the command line when starting and stopping the server. The Adapter work with both Windows and Linux based systems. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 06:29:27 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 30 Jun 2014 06:29:27 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-453) Support Apache HTTPD as a DeployableContainer in Managed mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980570#comment-12980570 ] Stefan Miklosovic commented on ARQ-453: --------------------------------------- [~ozizka] [~rrajesh] ([~aslak]) feel free to extend https://github.com/smiklosovic/arquillian-container-apache, I am done with this as I do not know how to advance with problems I described there, maybe some topic for gsoc or bachelor thesis? > Support Apache HTTPD as a DeployableContainer in Managed mode > ------------------------------------------------------------- > > Key: ARQ-453 > URL: https://issues.jboss.org/browse/ARQ-453 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Apache HTTPD Containers > Reporter: Ondrej Zizka > Fix For: httpd_1.0.0.next > > > The DeployableContainer interface provided by Arquillian offer a simple abstraction over something that you can setup, start or stop. In addition it can support deploy and undeploy. > The same logic can be applied to pure services, e.g. Mail, Database or FTP servers. > The Apache HTTPD server adapter is a DeployableContainer implementation that control the lifecycle of a local Apache HTTP Server. The Adapter support adding additional HTTPD configuration during setup, and rely on calling out to the command line when starting and stopping the server. The Adapter work with both Windows and Linux based systems. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 08:11:24 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 30 Jun 2014 08:11:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980600#comment-12980600 ] Luk?? Fry? commented on ARQ-1728: --------------------------------- This is interesting problem, maybe we should bring it to forums? > Add possibility to report AS console output related to test methods > ------------------------------------------------------------------- > > Key: ARQ-1728 > URL: https://issues.jboss.org/browse/ARQ-1728 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > > There is not any possiblity to see what AS has written out to console with test methods. > Investigate a way how to match output from AS with particular test method during which that console output has occured. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 11:49:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 30 Jun 2014 11:49:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980719#comment-12980719 ] Juraj H?ska commented on ARQGRA-454: ------------------------------------ Hello Juergen, all tests for Graphene work with Arquillian core {{1.1.5.Final}} and {{Arquillian Drone 1.3.1.Final}}. Could you please provide us a test case where you are getting this error ? > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 11:49:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 30 Jun 2014 11:49:24 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980719#comment-12980719 ] Juraj H?ska edited comment on ARQGRA-454 at 6/30/14 11:49 AM: -------------------------------------------------------------- Hello Juergen, all tests for Graphene pass with Arquillian core {{1.1.5.Final}} and {{Arquillian Drone 1.3.1.Final}}. Could you please provide us a test case where you are getting this error ? was (Author: jhuska): Hello Juergen, all tests for Graphene work with Arquillian core {{1.1.5.Final}} and {{Arquillian Drone 1.3.1.Final}}. Could you please provide us a test case where you are getting this error ? > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 18:12:35 2014 From: issues at jboss.org (MINNA HU (JIRA)) Date: Mon, 30 Jun 2014 18:12:35 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-197) Research support for @Deployment on multiple levels In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980801#comment-12980801 ] MINNA HU commented on ARQ-197: ------------------------------ Our team is using Arquillian for our feature test, we would like to deploy the whole system at one time, and then run test classes that are created for different features. It will be really helpful to run @Deployment at test suite level. If the community can fix this feature test, it will benefit lots of users. Thank you~ > Research support for @Deployment on multiple levels > --------------------------------------------------- > > Key: ARQ-197 > URL: https://issues.jboss.org/browse/ARQ-197 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Aslak Knutsen > Priority: Critical > Fix For: 2.0.0.CR1 > > > One deployment pr TestCase might not always be the ideal solution. Research how we can deploy multiple TestCases with one Deployment and test them all at once. -- This message was sent by Atlassian JIRA (v6.2.6#6264)