From issues at jboss.org Thu Jul 2 06:12:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:12:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1962) Update Drone to use 2.46.0 Selenium In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1962: -------------------------------- Summary: Update Drone to use 2.46.0 Selenium Key: ARQ-1962 URL: https://issues.jboss.org/browse/ARQ-1962 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_2.0.0.Alpha4 Reporter: Karel Piwko Update to latest Selenium available -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:12:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:12:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1962) Update Drone to use 2.46.0 Selenium In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1962: ----------------------------- Fix Version/s: drone_2.0.0.Alpha5 > Update Drone to use 2.46.0 Selenium > ----------------------------------- > > Key: ARQ-1962 > URL: https://issues.jboss.org/browse/ARQ-1962 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha4 > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > Update to latest Selenium available -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:13:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:13:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1884) Update Selenium to 2.44.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1884. ---------------------------- Resolution: Out of Date Will be handled via ARQ-1962 > Update Selenium to 2.44.0 > ------------------------- > > Key: ARQ-1884 > URL: https://issues.jboss.org/browse/ARQ-1884 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2, drone_1.3.1.Final > Reporter: Karel Piwko > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:13:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:13:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1851) Update Selenium to 2.43.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1851. ---------------------------- Resolution: Out of Date Will be handled via ARQ-1962 > Update Selenium to 2.43.0 > ------------------------- > > Key: ARQ-1851 > URL: https://issues.jboss.org/browse/ARQ-1851 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.3.1.Final > Reporter: Pavol Pitonak > > Update to latest Selenium - 2.43.0 supporting new versions of browsers, e.g. Firefox 31 ESR -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:18:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:18:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1874) Allow Drone to skip session file creation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1874: ----------------------------- Fix Version/s: drone_2.0.0.Alpha5 > Allow Drone to skip session file creation > ----------------------------------------- > > Key: ARQ-1874 > URL: https://issues.jboss.org/browse/ARQ-1874 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > It should be possible not to touch filesystem and avoid creating session file if user wishes to do so. > Storage should be completely ignored if remoteReusable is not set. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:20:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:20:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1836) Support HtmlUnitDriver client options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1836: ----------------------------- Fix Version/s: drone_2.1.0.Final > Support HtmlUnitDriver client options > ------------------------------------- > > Key: ARQ-1836 > URL: https://issues.jboss.org/browse/ARQ-1836 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Fix For: drone_2.1.0.Final > > > There are options that could be set for HtmlUnitDriver but are not available in Drone configuration. > Drone would need to proxy HtmlUnitDriver and override protected {{modifyWebClient}} method because this is not exposed in Selenium. > https://code.google.com/p/selenium/source/browse/java/client/src/org/openqa/selenium/htmlunit/HtmlUnitDriver.java?r=1615e198f0e0b9d7a0cc60bedf475fe23b9c7e1e#266 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:21:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:21:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1890) Support implementation of Microsoft WebDriver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1890: ----------------------------- Fix Version/s: drone_2.1.0.Final > Support implementation of Microsoft WebDriver > --------------------------------------------- > > Key: ARQ-1890 > URL: https://issues.jboss.org/browse/ARQ-1890 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.3.1.Final > Reporter: Sona Jamborova > Fix For: drone_2.1.0.Final > > > Selenium team adds support of Microsoft WebDriver in 2.43.0. Drone should use this vendor as well as selenium. > My Idea is: > 1) An user is responsible to install MS WebDriver > 2) Arquillian.xml presents new property (for example: IEDriverEngine). The values are LEGACY, VENDOR, AUTODETECT. The default value is LEGACY or AUTODETECT. I prefer AUTODETECT. > Unfortunately, this feature is not fully supported by Selenium for Java platforms (see comments). > Solution for branch drone 1.3.x: > * for enabling property in arquillian.xml: > ** add new field (attribute) in class WebDriverConfiguration > ** add setter and getter for this field > ** Note: properties in arquillian.xml are automaticaly mapped to fields in this class > * map a value of ieDriverEngine property to system property "webdriver.ie.driver.engine" > ** in class InternetExplorerDriverFactory -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:21:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:21:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1826) Download Explorer binary for Drone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1826: ----------------------------- Fix Version/s: drone_2.1.0.Final > Download Explorer binary for Drone > ---------------------------------- > > Key: ARQ-1826 > URL: https://issues.jboss.org/browse/ARQ-1826 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Stefan Miklosovic > Fix For: drone_2.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:23:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:23:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1823) ChromeBinary is not picked by ChromeDriver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085716#comment-13085716 ] Karel Piwko commented on ARQ-1823: ---------------------------------- Related: https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/ChromeDriverFactory.java#L95 > ChromeBinary is not picked by ChromeDriver > ------------------------------------------ > > Key: ARQ-1823 > URL: https://issues.jboss.org/browse/ARQ-1823 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > It looks like that capability is not used by upstream implementation. We need to make it a part of ChromeOptions instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:23:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:23:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1823) ChromeBinary is not picked by ChromeDriver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1823: ----------------------------- Fix Version/s: drone_2.0.0.Alpha5 > ChromeBinary is not picked by ChromeDriver > ------------------------------------------ > > Key: ARQ-1823 > URL: https://issues.jboss.org/browse/ARQ-1823 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > It looks like that capability is not used by upstream implementation. We need to make it a part of ChromeOptions instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:24:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:24:02 -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 ] Karel Piwko closed ARQ-1795. ---------------------------- Resolution: Out of Date There is not going to be any significant updates on 1.3.x branch. > Update ghostdriver and phantom driver for Drone > ----------------------------------------------- > > Key: ARQ-1795 > URL: https://issues.jboss.org/browse/ARQ-1795 > Project: Arquillian > Issue Type: Task > 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.3.15#6346) From issues at jboss.org Thu Jul 2 06:25:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:25:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1775) Allow to disable/enable nativeEvents via arquillian.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1775: ----------------------------- Fix Version/s: drone_2.0.0.Alpha5 > Allow to disable/enable nativeEvents via arquillian.xml > ------------------------------------------------------- > > Key: ARQ-1775 > URL: https://issues.jboss.org/browse/ARQ-1775 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Sona Jamborova > Fix For: drone_2.0.0.Alpha5 > > > Selenium 2 allows to enable/disable nativeEvents for WebDriver. This feature should be set before initialization of WebDriver instance. See: > FirefoxProfile profile = new FirefoxProfile(); > profile.setEnableNativeEvents(true); > WebDriver driver = new FirefoxDriver(profile); > Drone injects instance of FirefoxDriver and I have not any option how disable native Events for Firefox and Windows. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:28:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:28:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1743) Merge configuration and callable creation together In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085719#comment-13085719 ] Karel Piwko commented on ARQ-1743: ---------------------------------- https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-impl/src/main/java/org/jboss/arquillian/drone/impl/DroneConfigurator.java#L85 > Merge configuration and callable creation together > -------------------------------------------------- > > Key: ARQ-1743 > URL: https://issues.jboss.org/browse/ARQ-1743 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Karel Piwko > Fix For: drone_2.0.0.Beta1 > > > There should be just one event and either both or none of the object should be present. > This mean that callable and configuration should be created at the same time. This would make usage of Drone much easier. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:29:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:29:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1639) Enable UnusedImports in checkstyle rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085720#comment-13085720 ] Karel Piwko commented on ARQ-1639: ---------------------------------- https://github.com/arquillian/arquillian-extension-drone/blob/master/build-config/src/main/resources/arquillian-drone-checkstyle/checkstyle.xml#L25 Related to version of the checkstyle plugin. > Enable UnusedImports in checkstyle rules > ---------------------------------------- > > Key: ARQ-1639 > URL: https://issues.jboss.org/browse/ARQ-1639 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Fix For: drone_2.0.0.Beta1 > > > Checkstyle now supports scanning JavaDoc for imports. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:30:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:30:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1639) Enable UnusedImports in checkstyle rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1639: ----------------------------- Fix Version/s: drone_2.0.0.Alpha5 (was: drone_2.0.0.Beta1) > Enable UnusedImports in checkstyle rules > ---------------------------------------- > > Key: ARQ-1639 > URL: https://issues.jboss.org/browse/ARQ-1639 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > Checkstyle now supports scanning JavaDoc for imports. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:33:04 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:33:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1545) Drone: allow to setup WebDriver's Capabilities programatically In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1545: ----------------------------- Fix Version/s: drone_2.1.0.Final (was: drone_2.0.0.Beta1) > Drone: allow to setup WebDriver's Capabilities programatically > -------------------------------------------------------------- > > Key: ARQ-1545 > URL: https://issues.jboss.org/browse/ARQ-1545 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Luk?? Fry? > Fix For: drone_2.1.0.Final > > > The programatic configuration comes when some capability is unsupported and it has complex type, such as collection or array. > ---- > Even though I can access WebDriverConfiguration programatically and retrieve #getCapabilities(), I will get clone of capabilities stored in configuration. > I suggest we allow to access capabilityMap in order to allow programatically configure. > ---- > Please document a sample of usage here once done, i.e. what even is expected to listen. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:39:04 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:39:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1340) Drone webdriver is not created during @BeforeClass In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085725#comment-13085725 ] Karel Piwko commented on ARQ-1340: ---------------------------------- To be retested with latest core as a part of beta1 testing. > Drone webdriver is not created during @BeforeClass > -------------------------------------------------- > > Key: ARQ-1340 > URL: https://issues.jboss.org/browse/ARQ-1340 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_1.1.1.Final > Environment: Arquillian JUnit Container 1.0.3.Final > Arquillian Graphene Webdriver 2.0.0.Alpha3 > Arquillian Drone dependencies and Selenium dependencies 1.1.1.Final > Arquillian Core dependencies 1.0.3.Final > junit 4.8.1 > jdk 1.6 > Reporter: Alex Okrushko > Fix For: drone_2.0.0.Beta1 > > > Drone webdriver is not created during @BeforeClass, however *is created during @Before or if called by GrapheneContext.getProxy()* > The following does NOT work: > {code:java} > @RunWith(Arquillian.class) > public class TestDroneLogin { > @Drone > private static WebDriver driver; > > @BeforeClass > public static void setup(){ > //GrapheneContext.getProxy().navigate().to("http://google.com"); > driver.navigate().to("http://google.com"); > } > > @Test > public void testInput(){ > driver.findElement(By.cssSelector("input#gbqfq")); > } > } > {code} > However, if I use {{GrapheneContext.getProxy()}} instead of {{driver}}, everything works as expected: > {code:java} > @BeforeClass > public static void setup(){ > GrapheneContext.getProxy().navigate().to("http://google.com"); > } > {code} > ALSO, if {{@Before}} is used then Drone webdriver is created as expected, so this problem is specific to {{@BeforeClass}} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:39:05 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:39:05 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1264) Drone: provide Chrome driver binary from Maven In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1264: ----------------------------- Fix Version/s: drone_2.1.0.Final (was: drone_2.0.0.Beta1) > Drone: provide Chrome driver binary from Maven > ---------------------------------------------- > > Key: ARQ-1264 > URL: https://issues.jboss.org/browse/ARQ-1264 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Luk?? Fry? > Labels: usability > Fix For: drone_2.1.0.Final > > > It should be packaged in JAR and installed to drive similarly how we do it with PhantomJS. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:40:04 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:40:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1176) automatically take screenshot and capture the html output on Assert failure or Exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1176. ---------------------------- Resolution: Rejected Rejecting, please use Arquillian Recorder extension instead. > automatically take screenshot and capture the html output on Assert failure or Exception > ---------------------------------------------------------------------------------------- > > Key: ARQ-1176 > URL: https://issues.jboss.org/browse/ARQ-1176 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Mark Struberg > Fix For: drone_2.0.0.Beta1 > > > Some testing frameworks like cucumber automatically takes a screenshot and stores the current html output when test failure occurs. > Imo this is a great feature as it is really hard to find out what went wrong without having any information at hand. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:41:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:41:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1179) Mark a test so it will only run against certain browsers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1179: ----------------------------- Fix Version/s: drone_2.1.0.Final (was: drone_2.0.0.Beta1) > Mark a test so it will only run against certain browsers > -------------------------------------------------------- > > Key: ARQ-1179 > URL: https://issues.jboss.org/browse/ARQ-1179 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Brian Leathem > Fix For: drone_2.1.0.Final > > > It would be useful to be able to annotate a particular test so it will only run when driven by a particular set of browsers. > Some sample use cases: > # Some tests cannot target the incomplete js impl found in html unit. I would mark such tests not to run when htmlunit is the configured browser (in CI for instance) > # Some tests may target non-standard behaviour in certain browsers (older IE versions for instance) and may not make sense to run in all browsers. I would mark such tests not to run only when IE is the configured browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:42:09 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:42:09 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1077) Persistence Plugin does not work with Drone/Graphene In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1077: ----------------------------- Fix Version/s: drone_2.1.0.Final (was: drone_2.0.0.Beta1) > Persistence Plugin does not work with Drone/Graphene > ---------------------------------------------------- > > Key: ARQ-1077 > URL: https://issues.jboss.org/browse/ARQ-1077 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone, Extension - Persistence > Environment: JBoss AS 7 Container > Reporter: Bryan Saunders > Assignee: Bartosz Majsak > Labels: drone, persistence > Fix For: drone_2.1.0.Final > > > Persistence Extension does not execute when being used with the Drone/Graphene extensions. When you run the tests in Client Mode the @UsingDataSet annotations do not trigger and populate the database. @ApplyScriptBefore also does not work. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:43:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:43:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1699) PhantomJS resolution by Spacelift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1699: ----------------------------- Fix Version/s: drone_2.1.0.Final (was: drone_2.0.0.Beta1) > PhantomJS resolution by Spacelift > --------------------------------- > > Key: ARQ-1699 > URL: https://issues.jboss.org/browse/ARQ-1699 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_2.1.0.Final > > > PhantomJS resolution should be done via Spacelift. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:43:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:43:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1695) Integrate Spacelift into Drone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1695: ----------------------------- Fix Version/s: drone_2.1.0.Final (was: drone_2.0.0.Beta1) > Integrate Spacelift into Drone > ------------------------------ > > Key: ARQ-1695 > URL: https://issues.jboss.org/browse/ARQ-1695 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_2.1.0.Final > > > Spacelift can be used for following tasks: > * Download and execution of Selenium Server > * Download of ChromeDriver binary > * Download of IEDriver binary (optional, might not be needed as of IE11+) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:48:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:48:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1693) Independent and flexible lifecycle for Drones In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1693: ----------------------------- Fix Version/s: drone_2.1.0.Final (was: drone_2.0.0.Beta1) > Independent and flexible lifecycle for Drones > --------------------------------------------- > > Key: ARQ-1693 > URL: https://issues.jboss.org/browse/ARQ-1693 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_2.1.0.Final > > > It should be possible to define lifecycle that is independent of existing Arquillian events. > Suite being one of the most prominent ones. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:51:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:51:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1692) Factories should not bring runtime dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085733#comment-13085733 ] Karel Piwko commented on ARQ-1692: ---------------------------------- Maybe try/catch here and other related registered objects would help: https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-impl/src/main/java/org/jboss/arquillian/drone/impl/DroneRegistrar.java#L78 > Factories should not bring runtime dependencies > ----------------------------------------------- > > Key: ARQ-1692 > URL: https://issues.jboss.org/browse/ARQ-1692 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_2.0.0.Beta1 > > > DroneFactories should fail graciously in case that Drone type they are trying to instantiate are not on classpath. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:52:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:52:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1690) Provide and API/SPI to solve backward compatibility In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1690. ---------------------------- Resolution: Won't Fix Users will be left with migration documentations. > Provide and API/SPI to solve backward compatibility > --------------------------------------------------- > > Key: ARQ-1690 > URL: https://issues.jboss.org/browse/ARQ-1690 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > > For extension relying on Drone 1.2.x, migration to 2.0.0 should be smooth. Identify what API/SPI needs to be supported based on existing extensions: > These are at least: > * Graphene 2 > * Warp > * JBehave > * CukeSpace > * APE > * SauceLabs > Note, likely we won't be able to support backwards compatibility 100%. We rather need to make sure major extensions using Drone stay compatible or provide a very easy migration path, e.g. Drone compatibility package. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:52:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:52:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1690) Provide and API/SPI to solve backward compatibility In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1690: ----------------------------- Fix Version/s: (was: drone_2.0.0.Beta1) > Provide and API/SPI to solve backward compatibility > --------------------------------------------------- > > Key: ARQ-1690 > URL: https://issues.jboss.org/browse/ARQ-1690 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > > For extension relying on Drone 1.2.x, migration to 2.0.0 should be smooth. Identify what API/SPI needs to be supported based on existing extensions: > These are at least: > * Graphene 2 > * Warp > * JBehave > * CukeSpace > * APE > * SauceLabs > Note, likely we won't be able to support backwards compatibility 100%. We rather need to make sure major extensions using Drone stay compatible or provide a very easy migration path, e.g. Drone compatibility package. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:53:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:53:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1689) Drop Android and iOS Drivers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1689: ----------------------------- Fix Version/s: drone_2.0.0.Alpha5 > Drop Android and iOS Drivers > ---------------------------- > > Key: ARQ-1689 > URL: https://issues.jboss.org/browse/ARQ-1689 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > Drop AndroidDriver and iPhoneDriver, as they were dropped from upstream Selenium. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:53:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:53:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1008) Can't use reusable remote driver with opera In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1008: ----------------------------- Fix Version/s: (was: drone_2.0.0.Beta1) > Can't use reusable remote driver with opera > ------------------------------------------- > > Key: ARQ-1008 > URL: https://issues.jboss.org/browse/ARQ-1008 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_1.1.0.CR2 > Reporter: Jan Papousek > Assignee: Jan Papousek > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.arquillian.drone.webdriver.example.WebDriverTestCase > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.303 sec <<< FAILURE! > org.jboss.arquillian.drone.webdriver.example.WebDriverTestCase Time elapsed: 0 sec <<< ERROR! > org.openqa.selenium.WebDriverException: Address already in use > Command duration or timeout: 1.50 seconds > Build info: version: '2.24.1', revision: '17205', time: '2012-06-19 15:28:49' > System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.43.8-1.fc15.x86_64', java.version: '1.7.0_04' > Driver info: driver.version: RemoteWebDriver > Session ID: > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:188) > at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145) > at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472) > at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:155) > at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:107) > at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:115) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createRemoteDriver(RemoteWebDriverFactory.java:135) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createReusableDriver(RemoteWebDriverFactory.java:162) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:95) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:49) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:129) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:43) > at org.jboss.arquillian.drone.impl.DroneCreator.createWebTestBrowser(DroneCreator.java:71) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java: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.drone.impl.DroneConfigurator.configureDrone(DroneConfigurator.java:116) > 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:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) > Caused by: java.net.BindException: Address already in use > at sun.nio.ch.Net.bind0(Native Method) > at sun.nio.ch.Net.bind(Net.java:344) > at sun.nio.ch.Net.bind(Net.java:336) > at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199) > at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) > at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) > at com.opera.core.systems.scope.stp.StpConnectionListener.start(StpConnectionListener.java:95) > at com.opera.core.systems.scope.stp.StpConnectionListener.(StpConnectionListener.java:58) > at com.opera.core.systems.scope.stp.StpThread.(StpThread.java:46) > at com.opera.core.systems.ScopeServices.(ScopeServices.java:112) > at com.opera.core.systems.OperaDriver.createScopeServices(OperaDriver.java:251) > at com.opera.core.systems.OperaDriver.init(OperaDriver.java:197) > at com.opera.core.systems.OperaDriver.start(OperaDriver.java:186) > at com.opera.core.systems.OperaDriver.(OperaDriver.java:178) > at com.opera.core.systems.OperaDriver.(OperaDriver.java:160) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at org.openqa.selenium.remote.server.DefaultDriverFactory.callConstructor(DefaultDriverFactory.java:57) > at org.openqa.selenium.remote.server.DefaultDriverFactory.newInstance(DefaultDriverFactory.java:51) > at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:196) > at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:1) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:150) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:54:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:54:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1008) Can't use reusable remote driver with opera In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1008. ---------------------------- Resolution: Out of Date Support for old Opera browser will not get any maintenance anymore. > Can't use reusable remote driver with opera > ------------------------------------------- > > Key: ARQ-1008 > URL: https://issues.jboss.org/browse/ARQ-1008 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_1.1.0.CR2 > Reporter: Jan Papousek > Assignee: Jan Papousek > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.arquillian.drone.webdriver.example.WebDriverTestCase > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.303 sec <<< FAILURE! > org.jboss.arquillian.drone.webdriver.example.WebDriverTestCase Time elapsed: 0 sec <<< ERROR! > org.openqa.selenium.WebDriverException: Address already in use > Command duration or timeout: 1.50 seconds > Build info: version: '2.24.1', revision: '17205', time: '2012-06-19 15:28:49' > System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.43.8-1.fc15.x86_64', java.version: '1.7.0_04' > Driver info: driver.version: RemoteWebDriver > Session ID: > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:188) > at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145) > at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472) > at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:155) > at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:107) > at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:115) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createRemoteDriver(RemoteWebDriverFactory.java:135) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createReusableDriver(RemoteWebDriverFactory.java:162) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:95) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:49) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:129) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:43) > at org.jboss.arquillian.drone.impl.DroneCreator.createWebTestBrowser(DroneCreator.java:71) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java: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.drone.impl.DroneConfigurator.configureDrone(DroneConfigurator.java:116) > 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:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) > Caused by: java.net.BindException: Address already in use > at sun.nio.ch.Net.bind0(Native Method) > at sun.nio.ch.Net.bind(Net.java:344) > at sun.nio.ch.Net.bind(Net.java:336) > at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199) > at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) > at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) > at com.opera.core.systems.scope.stp.StpConnectionListener.start(StpConnectionListener.java:95) > at com.opera.core.systems.scope.stp.StpConnectionListener.(StpConnectionListener.java:58) > at com.opera.core.systems.scope.stp.StpThread.(StpThread.java:46) > at com.opera.core.systems.ScopeServices.(ScopeServices.java:112) > at com.opera.core.systems.OperaDriver.createScopeServices(OperaDriver.java:251) > at com.opera.core.systems.OperaDriver.init(OperaDriver.java:197) > at com.opera.core.systems.OperaDriver.start(OperaDriver.java:186) > at com.opera.core.systems.OperaDriver.(OperaDriver.java:178) > at com.opera.core.systems.OperaDriver.(OperaDriver.java:160) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at org.openqa.selenium.remote.server.DefaultDriverFactory.callConstructor(DefaultDriverFactory.java:57) > at org.openqa.selenium.remote.server.DefaultDriverFactory.newInstance(DefaultDriverFactory.java:51) > at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:196) > at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:1) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:150) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:55:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:55:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-838) Allow Arquillian Drone to handle Robotium In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-838. --------------------------- Resolution: Rejected Robotium could be handled by Droidium project instead. If you want to have it there, feel free to open new issue. > Allow Arquillian Drone to handle Robotium > ----------------------------------------- > > Key: ARQ-838 > URL: https://issues.jboss.org/browse/ARQ-838 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Aleksey Shilin > > Robotium is a Java based framework for testing Android applications using a high level API. > Once the integration with Android integration tests is done, it would be convenient to have its support in Arquillian Drone. > The key here is to grab current activity from Android context and provide a Solo object which could be injected into test itself. > The usage might look similar to the following: > {code} > @RunWith(Arquillian.class) > public class AndroidTest { > > @Test > public void androidActivity(@AndroidActivity HelloAndroid helloAndroid, @Drone Solo solo) { > solo.sendKey(Solo.MENU); > solo.clickOnText("More"); > solo.clickOnText("Preferences"); > solo.clickOnText("Edit File Extensions"); > Assert.assertTrue(solo.searchText("rtf")); > } > } > {code} > Note that the above example does not reflect possible usage of Android/Robotium in class level, this a method-level proposal. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:57:02 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:57:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-437) Introduce annotation to control lifecycle of selenium session In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-437: ---------------------------- Fix Version/s: drone_2.1.0.Final (was: drone_2.0.0.Beta1) > Introduce annotation to control lifecycle of selenium session > ------------------------------------------------------------- > > Key: ARQ-437 > URL: https://issues.jboss.org/browse/ARQ-437 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Luk?? Fry? > Fix For: drone_2.1.0.Final > > > Following options are being considered: > BEFORE_SUITE > BEFORE_CLASS > BEFORE_METHOD -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 06:58:03 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 06:58:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-435) Add @FailureLogging feature and appropriate listener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-435. --------------------------- Fix Version/s: (was: drone_2.0.0.Beta1) Resolution: Out of Date Now the functionality is handled by Recorder extension. > Add @FailureLogging feature and appropriate listener > ---------------------------------------------------- > > Key: ARQ-435 > URL: https://issues.jboss.org/browse/ARQ-435 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: 1.0.0.Alpha5 > Reporter: Luk?? Fry? > > Get inspired in formet Ajocado's implementation: > https://github.com/arquillian/arquillian-ajocado/blob/1.0.0.Alpha2/testng/src/main/java/org/jboss/arquillian/ajocado/testng/listener/FailureLoggingTestListener.java -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 07:00:07 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 2 Jul 2015 07:00:07 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1694) Update Saucelabs extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1694: ----------------------------- Fix Version/s: drone_2.0.0.Final (was: drone_2.0.0.Beta1) > Update Saucelabs extension > -------------------------- > > Key: ARQ-1694 > URL: https://issues.jboss.org/browse/ARQ-1694 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_2.0.0.Final > > > Provide working SauceLabs extension fully compatible with Drone 2. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 9 05:19:04 2015 From: issues at jboss.org (Christian Schulz (JIRA)) Date: Thu, 9 Jul 2015 05:19:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1963) Original exception lost when thrown from @Before-annotated method In-Reply-To: References: Message-ID: Christian Schulz created ARQ-1963: ------------------------------------- Summary: Original exception lost when thrown from @Before-annotated method Key: ARQ-1963 URL: https://issues.jboss.org/browse/ARQ-1963 Project: Arquillian Issue Type: Bug Components: Base Implementation Reporter: Christian Schulz I have recognized that there seems to be an issue with JUnit and Arquillian. If there is an exception in @before-annotated method, it seems to be lost. There is no entry in the log neither the test will be aborted instantly. {code} @Before public void preparePersistenceTest() { throw new RuntimeException("test"); {code} A NPE occurs in @after-annotated method. The @test-annotated method doesn't fail fast. Here the console output: {code} Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.979 sec <<< FAILURE! - in RelocateTest relocateSuccessful(RelocateTest) Time elapsed: 0.24 1 sec <<< ERROR! java.lang.NullPointerException: null at RelocateTest.clearData(PackageRelocateTest.java:77) {code} *The issue* testFailure in ExpectedExceptionHolder is notified and overwrite an existing exception https://github.com/arquillian/arquillian-core/blob/e39433696861f11588180894378c32f795da8085/junit/container/src/main/java/org/jboss/arquillian/junit/container/JUnitTestRunner.java#L110 This exception is used to create the testresult: https://github.com/arquillian/arquillian-core/blob/e39433696861f11588180894378c32f795da8085/junit/container/src/main/java/org/jboss/arquillian/junit/container/JUnitTestRunner.java#L70 In my opinion there are two ways to handle this issue: - Don't overwrite an existing exception and discard the new exception - Change the TestResult class to hold multiple exceptions The first approach could be implemented very fast. I can't imagine a case when other exceptions are really needed. I would say other exceptions occur because the first exception occurred. https://github.com/arquillian/arquillian-core/issues/86 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 9 05:20:03 2015 From: issues at jboss.org (Christian Schulz (JIRA)) Date: Thu, 9 Jul 2015 05:20:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1963) Original exception lost when thrown from @Before-annotated method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulz updated ARQ-1963: ---------------------------------- Steps to Reproduce: Throw an exception in the before method. (was: {code} @RunWith(Arquillian.class) public class ExceptionTest { private Integer quantity; @Deployment public static Archive createDeployment() { return ShrinkWrap.create(WebArchive.class); } @Before public void preparePersistenceTest() { quantity = null; throw new RuntimeException("test"); } @Test public void adjustSuccessful() { assertTrue(quantity == null); } @After public void clearData() throws Exception { quantity.compareTo(1); } } {code}) > Original exception lost when thrown from @Before-annotated method > ----------------------------------------------------------------- > > Key: ARQ-1963 > URL: https://issues.jboss.org/browse/ARQ-1963 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Reporter: Christian Schulz > > I have recognized that there seems to be an issue with JUnit and Arquillian. > If there is an exception in @before-annotated method, it seems to be lost. There is no entry in the log neither the test will be aborted instantly. > {code} > @Before > public void preparePersistenceTest() { > throw new RuntimeException("test"); > {code} > A NPE occurs in @after-annotated method. The @test-annotated method doesn't fail fast. > Here the console output: > {code} > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.979 sec <<< FAILURE! - in RelocateTest > relocateSuccessful(RelocateTest) Time elapsed: 0.24 > 1 sec <<< ERROR! > java.lang.NullPointerException: null > at RelocateTest.clearData(PackageRelocateTest.java:77) > {code} > *The issue* > testFailure in ExpectedExceptionHolder is notified and overwrite an existing exception https://github.com/arquillian/arquillian-core/blob/e39433696861f11588180894378c32f795da8085/junit/container/src/main/java/org/jboss/arquillian/junit/container/JUnitTestRunner.java#L110 > This exception is used to create the testresult: > https://github.com/arquillian/arquillian-core/blob/e39433696861f11588180894378c32f795da8085/junit/container/src/main/java/org/jboss/arquillian/junit/container/JUnitTestRunner.java#L70 > In my opinion there are two ways to handle this issue: > - Don't overwrite an existing exception and discard the new exception > - Change the TestResult class to hold multiple exceptions > The first approach could be implemented very fast. I can't imagine a case when other exceptions are really needed. I would say other exceptions occur because the first exception occurred. > https://github.com/arquillian/arquillian-core/issues/86 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 10 07:35:02 2015 From: issues at jboss.org (Sanne Grinovero (JIRA)) Date: Fri, 10 Jul 2015 07:35:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1964) OperateOnDeployment not honored when using the JMX Protocol In-Reply-To: References: Message-ID: Sanne Grinovero created ARQ-1964: ------------------------------------ Summary: OperateOnDeployment not honored when using the JMX Protocol Key: ARQ-1964 URL: https://issues.jboss.org/browse/ARQ-1964 Project: Arquillian Issue Type: Bug Affects Versions: 1.1.8.Final Reporter: Sanne Grinovero I was using protocol type {{jmx-as7}} to run tests on WildFly 9.0.0.Final, using 1.1.8.Final of Arquillian, and having the wildfly components aligned with the same versions I've found in WildFly 9's source code. It seems like a random deployed is chosen, and all tests in the same class are run on that same deployment rather than on the ones I'm specifying with {{@OperateOnDeployment}}. Switching to protocol {{Servlet 3.0}} seems to workaround the problem. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 13 03:54:03 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 13 Jul 2015 03:54:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-473) ClassNotFoundException: org.openqa.selenium.html5.DatabaseStorage with Selenium 2.46.0 In-Reply-To: References: Message-ID: Matous Jobanek created ARQGRA-473: ------------------------------------- Summary: ClassNotFoundException: org.openqa.selenium.html5.DatabaseStorage with Selenium 2.46.0 Key: ARQGRA-473 URL: https://issues.jboss.org/browse/ARQGRA-473 Project: Arquillian Graphene Issue Type: Bug Affects Versions: 2.1.0.Alpha2 Reporter: Matous Jobanek Graphene is not compatible with the latest Selenium 2.46.0. It throws {{ClassNotFoundException: org.openqa.selenium.html5.DatabaseStorage}} DatabaseStorage is deprecated class, that is not included it the latest Selenium. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 13 14:26:02 2015 From: issues at jboss.org (Dave Westerman (JIRA)) Date: Mon, 13 Jul 2015 14:26:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089014#comment-13089014 ] Dave Westerman commented on ARQ-1961: ------------------------------------- Gerhard, I created a workaround where I took the source code, and changed it to use the deleteOnExit(), and also to not fail if it can't delete the archive (since the deleteOnExit does get rid of it). I have added that to our own local repository, and am using that to get past my problem. I must be using more Arquillian functionality than my colleagues, because none of them have run into this problem (at least not yet). I am getting another error which may or may not be related (since again, none of my colleagues are running into it). But I will post in the forum first, since it's not necessarily related. > Exception while undeploying application in WebSphere Liberty Profile > -------------------------------------------------------------------- > > Key: ARQ-1961 > URL: https://issues.jboss.org/browse/ARQ-1961 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: OS: Windows 7 Professional > Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final > org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2 > Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1 > WebSphere Liberty Profile: 8.5.5.4 > JUnit: 4.11 > Java: IBM Java 1.7 in 1.6 mode > Reporter: Dave Westerman > Assignee: Gerhard Poul > Attachments: DaveWesterman_arquillian-enhanced-trace.zip > > > I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. > > All the tests run successfully. However, the JUnit test process always ends with an exception: > > org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > ... > Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy > FINER: ENTRY > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: ENTRY > [AUDIT ] CWWKG0016I: Starting server configuration update. > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml > [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. > [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ > [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. > [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] > [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. > [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. > [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: RETURN > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory > FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: ENTRY > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: RETURN -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 13 16:26:02 2015 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 13 Jul 2015 16:26:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089047#comment-13089047 ] Gerhard Poul commented on ARQ-1961: ----------------------------------- [~dlwester] This is interesting; I assume your colleagues use Windows as well? Can you check whether they have the same WLP build and configuration? Also interesting would be whether there is any obvious difference in terms of Java version, backup or anti-virus software between those machines? The problem with deleteOnExit() is that Liberty will not undeploy the code until we delete it from the apps directory. Do you maybe have the time to increase the timeout, reproduce the issue, and look at it in process explorer to find out which process is locking the file on your machine? > Exception while undeploying application in WebSphere Liberty Profile > -------------------------------------------------------------------- > > Key: ARQ-1961 > URL: https://issues.jboss.org/browse/ARQ-1961 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: OS: Windows 7 Professional > Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final > org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2 > Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1 > WebSphere Liberty Profile: 8.5.5.4 > JUnit: 4.11 > Java: IBM Java 1.7 in 1.6 mode > Reporter: Dave Westerman > Assignee: Gerhard Poul > Attachments: DaveWesterman_arquillian-enhanced-trace.zip > > > I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. > > All the tests run successfully. However, the JUnit test process always ends with an exception: > > org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > ... > Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy > FINER: ENTRY > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: ENTRY > [AUDIT ] CWWKG0016I: Starting server configuration update. > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml > [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. > [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ > [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. > [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] > [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. > [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. > [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: RETURN > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory > FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: ENTRY > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: RETURN -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 03:34:04 2015 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Tue, 14 Jul 2015 03:34:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-127) Verify TestNG Parallel test exeuction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089113#comment-13089113 ] Tomas Remes commented on ARQ-127: --------------------------------- I came across this as well. This problem manifests simply in the case when you specify some included group in the surefire plugin. The Arquillian @BeforeSuite method doesn't belong to this group (it seems that inheritGroups param is not evaluated at all. I am not sure why) so it's not executed. Simple workaround in this case is to include also "arquillian" group. I am not sure if it is/ is not a testng bug. You can see https://github.com/cbeust/testng/issues/313 and https://github.com/cbeust/testng/issues/184 > Verify TestNG Parallel test exeuction > ------------------------------------- > > Key: ARQ-127 > URL: https://issues.jboss.org/browse/ARQ-127 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Performance, Test Harness Integration > Reporter: Aslak Knutsen > Assignee: St?le Pedersen > Priority: Critical > Fix For: 2.0.0.Beta1 > > Attachments: testng-parallel.zip > > > Verify that Arquillian behaves correctly when ran in TestNG Parallel modes. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 03:35:04 2015 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Tue, 14 Jul 2015 03:35:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-127) Verify TestNG Parallel test exeuction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089113#comment-13089113 ] Tomas Remes edited comment on ARQ-127 at 7/14/15 3:34 AM: ---------------------------------------------------------- I came across this as well. This problem manifests simply in the case when you specify some included testgroup in the surefire plugin. The Arquillian @BeforeSuite method doesn't belong to this testgroup (it seems that inheritGroups param is not evaluated at all. I am not sure why) so it's not executed. Simple workaround in this case is to include also "arquillian" group. I am not sure if it is/ is not a testng bug. You can see https://github.com/cbeust/testng/issues/313 and https://github.com/cbeust/testng/issues/184 was (Author: tremes): I came across this as well. This problem manifests simply in the case when you specify some included group in the surefire plugin. The Arquillian @BeforeSuite method doesn't belong to this group (it seems that inheritGroups param is not evaluated at all. I am not sure why) so it's not executed. Simple workaround in this case is to include also "arquillian" group. I am not sure if it is/ is not a testng bug. You can see https://github.com/cbeust/testng/issues/313 and https://github.com/cbeust/testng/issues/184 > Verify TestNG Parallel test exeuction > ------------------------------------- > > Key: ARQ-127 > URL: https://issues.jboss.org/browse/ARQ-127 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Performance, Test Harness Integration > Reporter: Aslak Knutsen > Assignee: St?le Pedersen > Priority: Critical > Fix For: 2.0.0.Beta1 > > Attachments: testng-parallel.zip > > > Verify that Arquillian behaves correctly when ran in TestNG Parallel modes. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 06:54:03 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 15 Jul 2015 06:54:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1962) Update Drone to use 2.46.0 Selenium In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089636#comment-13089636 ] Matous Jobanek commented on ARQ-1962: ------------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/1abce8e489bb3e3f91328146cbe4cf4ad7e0c3d2 > Update Drone to use 2.46.0 Selenium > ----------------------------------- > > Key: ARQ-1962 > URL: https://issues.jboss.org/browse/ARQ-1962 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha4 > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > Update to latest Selenium available -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 09:29:02 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 15 Jul 2015 09:29:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1962) Update Drone to use 2.46.0 Selenium In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089636#comment-13089636 ] Matous Jobanek edited comment on ARQ-1962 at 7/15/15 9:28 AM: -------------------------------------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/3072abcb8cea2cd35e6a685a2ba4f5bb4a24618e was (Author: mjobanek): Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/1abce8e489bb3e3f91328146cbe4cf4ad7e0c3d2 > Update Drone to use 2.46.0 Selenium > ----------------------------------- > > Key: ARQ-1962 > URL: https://issues.jboss.org/browse/ARQ-1962 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha4 > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > Update to latest Selenium available -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 19:10:02 2015 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 15 Jul 2015 19:10:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1965) Tomcat 7 Adapter rely on ContextHome constructor introduced in 7.0.52 In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1965: ---------------------------------- Summary: Tomcat 7 Adapter rely on ContextHome constructor introduced in 7.0.52 Key: ARQ-1965 URL: https://issues.jboss.org/browse/ARQ-1965 Project: Arquillian Issue Type: Bug Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR7 Reporter: Aslak Knutsen Tomcat 7 Adapter rely on Code from 7.0.52 https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-embedded-7/src/main/java/org/jboss/arquillian/container/tomcat/embedded/EmbeddedHostConfig.java#L81 and https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-embedded-7/src/main/java/org/jboss/arquillian/container/tomcat/embedded/Tomcat7EmbeddedContainer.java#L318 ContextHome(String, Boolean) is new in 7.0.52 but missing in previous versions. Use reflection to check if (String, Boolean) exists, else fall back to (String). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 19:30:02 2015 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 15 Jul 2015 19:30:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1965) Tomcat 7 Adapter rely on ContextHome constructor introduced in 7.0.52 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen reassigned ARQ-1965: ---------------------------------- Assignee: Aslak Knutsen > Tomcat 7 Adapter rely on ContextHome constructor introduced in 7.0.52 > --------------------------------------------------------------------- > > Key: ARQ-1965 > URL: https://issues.jboss.org/browse/ARQ-1965 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > > Tomcat 7 Adapter rely on Code from 7.0.52 > https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-embedded-7/src/main/java/org/jboss/arquillian/container/tomcat/embedded/EmbeddedHostConfig.java#L81 > and > https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-embedded-7/src/main/java/org/jboss/arquillian/container/tomcat/embedded/Tomcat7EmbeddedContainer.java#L318 > ContextHome(String, Boolean) is new in 7.0.52 but missing in previous versions. > Use reflection to check if (String, Boolean) exists, else fall back to (String). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 19:35:01 2015 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 15 Jul 2015 19:35:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1965) Tomcat 7 Adapter rely on ContextHome constructor introduced in 7.0.52 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1965: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-tomcat/pull/29 > Tomcat 7 Adapter rely on ContextHome constructor introduced in 7.0.52 > --------------------------------------------------------------------- > > Key: ARQ-1965 > URL: https://issues.jboss.org/browse/ARQ-1965 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > > Tomcat 7 Adapter rely on Code from 7.0.52 > https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-embedded-7/src/main/java/org/jboss/arquillian/container/tomcat/embedded/EmbeddedHostConfig.java#L81 > and > https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-embedded-7/src/main/java/org/jboss/arquillian/container/tomcat/embedded/Tomcat7EmbeddedContainer.java#L318 > ContextHome(String, Boolean) is new in 7.0.52 but missing in previous versions. > Use reflection to check if (String, Boolean) exists, else fall back to (String). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 16 07:09:02 2015 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 16 Jul 2015 07:09:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-474) Remove arquillian-graphene as no one uses it In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-474: --------------------------------- Summary: Remove arquillian-graphene as no one uses it Key: ARQGRA-474 URL: https://issues.jboss.org/browse/ARQGRA-474 Project: Arquillian Graphene Issue Type: Task Reporter: Luk?? Fry? Docs and tutorials mention graphene-webdriver depchain: https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options http://arquillian.org/guides/functional_testing_using_graphene/ The depchains are not used by EAP BOMs too: https://issues.jboss.org/browse/JDF-840 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 16 07:10:02 2015 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 16 Jul 2015 07:10:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-474) Remove arquillian-graphene as no one uses it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-474: ------------------------------ Fix Version/s: 2.1-Tracking > Remove arquillian-graphene as no one uses it > -------------------------------------------- > > Key: ARQGRA-474 > URL: https://issues.jboss.org/browse/ARQGRA-474 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Luk?? Fry? > Fix For: 2.1-Tracking > > > Docs and tutorials mention graphene-webdriver depchain: > https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options > http://arquillian.org/guides/functional_testing_using_graphene/ > The depchains are not used by EAP BOMs too: > https://issues.jboss.org/browse/JDF-840 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 16 09:49:05 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 16 Jul 2015 09:49:05 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-474) Remove arquillian-graphene as no one uses it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Matous Jobanek created pull request #12 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Remove arquillian-graphene as no one uses it > -------------------------------------------- > > Key: ARQGRA-474 > URL: https://issues.jboss.org/browse/ARQGRA-474 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Luk?? Fry? > Fix For: 2.1-Tracking > > > Docs and tutorials mention graphene-webdriver depchain: > https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options > http://arquillian.org/guides/functional_testing_using_graphene/ > The depchains are not used by EAP BOMs too: > https://issues.jboss.org/browse/JDF-840 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 20 09:49:04 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 20 Jul 2015 09:49:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1874) Allow Drone to skip session file creation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090822#comment-13090822 ] Matous Jobanek commented on ARQ-1874: ------------------------------------- I wasn't able to reproduce this bug. Actually, in case when the remoteReusable property is not set I don't see any way how the session file could be created. The file is created in this method: https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/remote/reusable/ReusedSessionPermanentFileStorage.java#L94-L100 that is called only if the PersistReusedSessionsEvent is fired. This event is fired from one place only: https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/RemoteWebDriverFactory.java#L138 This code is reachable when the InitializationParametersMap has a sessionId as a key: https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/RemoteWebDriverFactory.java#L133-L135 however the key sessionId is added only in the method: https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/RemoteWebDriverFactory.java#L153 and calling of this method is dependent on the condition {{configuration.isRemoteReusable()}}: https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/RemoteWebDriverFactory.java#L97-L98 So, from the structure of the code it seems that it behaves as expected. Maybe I'm missing something... > Allow Drone to skip session file creation > ----------------------------------------- > > Key: ARQ-1874 > URL: https://issues.jboss.org/browse/ARQ-1874 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > It should be possible not to touch filesystem and avoid creating session file if user wishes to do so. > Storage should be completely ignored if remoteReusable is not set. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 21 03:52:04 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 21 Jul 2015 03:52:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1874) Allow Drone to skip session file creation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1874. ---------------------------- Resolution: Cannot Reproduce Bug Thanks for the check [~mjobanek]. I guess it was then fixed in Alpha3 or Alpha4 version. Closing as Cannot Reproduce Bug. > Allow Drone to skip session file creation > ----------------------------------------- > > Key: ARQ-1874 > URL: https://issues.jboss.org/browse/ARQ-1874 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > It should be possible not to touch filesystem and avoid creating session file if user wishes to do so. > Storage should be completely ignored if remoteReusable is not set. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 21 03:53:04 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 21 Jul 2015 03:53:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1874) Allow Drone to skip session file creation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reopened ARQ-1874: ------------------------------ Assignee: Matous Jobanek Reopened to add assignee. > Allow Drone to skip session file creation > ----------------------------------------- > > Key: ARQ-1874 > URL: https://issues.jboss.org/browse/ARQ-1874 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Alpha5 > > > It should be possible not to touch filesystem and avoid creating session file if user wishes to do so. > Storage should be completely ignored if remoteReusable is not set. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 21 03:53:05 2015 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 21 Jul 2015 03:53:05 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1874) Allow Drone to skip session file creation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1874. ---------------------------- Resolution: Done > Allow Drone to skip session file creation > ----------------------------------------- > > Key: ARQ-1874 > URL: https://issues.jboss.org/browse/ARQ-1874 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Alpha5 > > > It should be possible not to touch filesystem and avoid creating session file if user wishes to do so. > Storage should be completely ignored if remoteReusable is not set. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 10:13:03 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 22 Jul 2015 10:13:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1823) ChromeBinary is not picked by ChromeDriver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091764#comment-13091764 ] Matous Jobanek commented on ARQ-1823: ------------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/29a426b22d5d4353ed2c65e9d373376273c3959f > ChromeBinary is not picked by ChromeDriver > ------------------------------------------ > > Key: ARQ-1823 > URL: https://issues.jboss.org/browse/ARQ-1823 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > It looks like that capability is not used by upstream implementation. We need to make it a part of ChromeOptions instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 06:15:08 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 23 Jul 2015 06:15:08 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1775) Allow to disable/enable nativeEvents via arquillian.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092113#comment-13092113 ] Matous Jobanek commented on ARQ-1775: ------------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/7ef14d865a413c3231d06153f6779b8ee58a685a > Allow to disable/enable nativeEvents via arquillian.xml > ------------------------------------------------------- > > Key: ARQ-1775 > URL: https://issues.jboss.org/browse/ARQ-1775 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Sona Jamborova > Fix For: drone_2.0.0.Alpha5 > > > Selenium 2 allows to enable/disable nativeEvents for WebDriver. This feature should be set before initialization of WebDriver instance. See: > FirefoxProfile profile = new FirefoxProfile(); > profile.setEnableNativeEvents(true); > WebDriver driver = new FirefoxDriver(profile); > Drone injects instance of FirefoxDriver and I have not any option how disable native Events for Firefox and Windows. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 08:09:03 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 23 Jul 2015 08:09:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1639) Enable UnusedImports in checkstyle rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092165#comment-13092165 ] Matous Jobanek commented on ARQ-1639: ------------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/7ef14d865a413c3231d06153f6779b8ee58a685a > Enable UnusedImports in checkstyle rules > ---------------------------------------- > > Key: ARQ-1639 > URL: https://issues.jboss.org/browse/ARQ-1639 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha5 > > > Checkstyle now supports scanning JavaDoc for imports. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 10:20:03 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 23 Jul 2015 10:20:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1962) Update Drone to use 2.46.0 Selenium In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-1962 started by Matous Jobanek. ------------------------------------------- > Update Drone to use 2.46.0 Selenium > ----------------------------------- > > Key: ARQ-1962 > URL: https://issues.jboss.org/browse/ARQ-1962 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Alpha5 > > > Update to latest Selenium available -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 10:20:03 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 23 Jul 2015 10:20:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1962) Update Drone to use 2.46.0 Selenium In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-1962 stopped by Matous Jobanek. ------------------------------------------- > Update Drone to use 2.46.0 Selenium > ----------------------------------- > > Key: ARQ-1962 > URL: https://issues.jboss.org/browse/ARQ-1962 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Alpha5 > > > Update to latest Selenium available -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 10:22:04 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 23 Jul 2015 10:22:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1823) ChromeBinary is not picked by ChromeDriver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQ-1823: ----------------------------------- Assignee: Matous Jobanek > ChromeBinary is not picked by ChromeDriver > ------------------------------------------ > > Key: ARQ-1823 > URL: https://issues.jboss.org/browse/ARQ-1823 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Alpha5 > > > It looks like that capability is not used by upstream implementation. We need to make it a part of ChromeOptions instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 10:22:04 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 23 Jul 2015 10:22:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1775) Allow to disable/enable nativeEvents via arquillian.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQ-1775: ----------------------------------- Assignee: Matous Jobanek > Allow to disable/enable nativeEvents via arquillian.xml > ------------------------------------------------------- > > Key: ARQ-1775 > URL: https://issues.jboss.org/browse/ARQ-1775 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Sona Jamborova > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Alpha5 > > > Selenium 2 allows to enable/disable nativeEvents for WebDriver. This feature should be set before initialization of WebDriver instance. See: > FirefoxProfile profile = new FirefoxProfile(); > profile.setEnableNativeEvents(true); > WebDriver driver = new FirefoxDriver(profile); > Drone injects instance of FirefoxDriver and I have not any option how disable native Events for Firefox and Windows. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 10:22:04 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 23 Jul 2015 10:22:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1639) Enable UnusedImports in checkstyle rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQ-1639: ----------------------------------- Assignee: Matous Jobanek > Enable UnusedImports in checkstyle rules > ---------------------------------------- > > Key: ARQ-1639 > URL: https://issues.jboss.org/browse/ARQ-1639 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Alpha5 > > > Checkstyle now supports scanning JavaDoc for imports. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 10:22:04 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 23 Jul 2015 10:22:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1689) Drop Android and iOS Drivers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQ-1689: ----------------------------------- Assignee: Matous Jobanek > Drop Android and iOS Drivers > ---------------------------- > > Key: ARQ-1689 > URL: https://issues.jboss.org/browse/ARQ-1689 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Alpha5 > > > Drop AndroidDriver and iPhoneDriver, as they were dropped from upstream Selenium. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 10:23:03 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 23 Jul 2015 10:23:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1689) Drop Android and iOS Drivers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek resolved ARQ-1689. --------------------------------- Resolution: Done It has been already dropped in https://github.com/arquillian/arquillian-extension-drone/commit/c8ffcc68d27111eb3af53c848796998ea394d290 > Drop Android and iOS Drivers > ---------------------------- > > Key: ARQ-1689 > URL: https://issues.jboss.org/browse/ARQ-1689 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Alpha5 > > > Drop AndroidDriver and iPhoneDriver, as they were dropped from upstream Selenium. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 27 03:10:03 2015 From: issues at jboss.org (Michael Kotten (JIRA)) Date: Mon, 27 Jul 2015 03:10:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-475) Support inheritance for page fragments delegating to WebElement In-Reply-To: References: Message-ID: Michael Kotten created ARQGRA-475: ------------------------------------- Summary: Support inheritance for page fragments delegating to WebElement Key: ARQGRA-475 URL: https://issues.jboss.org/browse/ARQGRA-475 Project: Arquillian Graphene Issue Type: Enhancement Components: core Affects Versions: 2.1.0.Alpha2, 2.0.3.Final Reporter: Michael Kotten Priority: Minor When implementing page fragments that extend WebElement as described in https://docs.jboss.org/author/display/ARQGRA2/Delegate+to+WebElement it is not possible to use superclasses for this construct. This is because the method {{isAboutToDelegateToWebElement}} in {{PageFragmentEnricher}} just searches the current class, but not the superclasses. I'm preparing a minor change for this currently. Hope to send the pull request soon. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 27 11:04:02 2015 From: issues at jboss.org (Michael Kotten (JIRA)) Date: Mon, 27 Jul 2015 11:04:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-476) Extend root element from GrapheneElement In-Reply-To: References: Message-ID: Michael Kotten created ARQGRA-476: ------------------------------------- Summary: Extend root element from GrapheneElement Key: ARQGRA-476 URL: https://issues.jboss.org/browse/ARQGRA-476 Project: Arquillian Graphene Issue Type: Enhancement Components: core Affects Versions: 2.1.0.Alpha2, 2.0.3.Final Reporter: Michael Kotten Priority: Minor Currently the root element in page fragments must extend WebElement. I would like to extend this, so it can also extend GrapheneElement. I'm preparing a pull request for this currently. Would be nice if this enhancement would make it to the next release. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:17:05 2015 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 28 Jul 2015 11:17:05 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-396) Check/review JDF web-UI quickstarts for Graphene reference usage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-396: ------------------------------ Original Estimate: 1 hour Remaining Estimate: 1 hour > Check/review JDF web-UI quickstarts for Graphene reference usage > ---------------------------------------------------------------- > > Key: ARQGRA-396 > URL: https://issues.jboss.org/browse/ARQGRA-396 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Luk?? Fry? > Assignee: Oliver Ki?? > Fix For: 2.0-Tracking > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:18:06 2015 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 28 Jul 2015 11:18:06 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-396) Check/review JDF web-UI quickstarts for Graphene reference usage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-396: ------------------------------ Sprint: Graphene 2.0.1 Sprint 1, Graphene 2.0.2 (was: Graphene 2.0.1 Sprint 1) > Check/review JDF web-UI quickstarts for Graphene reference usage > ---------------------------------------------------------------- > > Key: ARQGRA-396 > URL: https://issues.jboss.org/browse/ARQGRA-396 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Luk?? Fry? > Assignee: Oliver Ki?? > Fix For: 2.0-Tracking > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:22:03 2015 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 28 Jul 2015 11:22:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-476) Extend root element from GrapheneElement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-476: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/134 > Extend root element from GrapheneElement > ----------------------------------------- > > Key: ARQGRA-476 > URL: https://issues.jboss.org/browse/ARQGRA-476 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.3.Final, 2.1.0.Alpha2 > Reporter: Michael Kotten > Priority: Minor > > Currently the root element in page fragments must extend WebElement. I would like to extend this, so it can also extend GrapheneElement. I'm preparing a pull request for this currently. Would be nice if this enhancement would make it to the next release. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 21:24:02 2015 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 28 Jul 2015 21:24:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1966) Support ENV variables to configure Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1966: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/89 > Support ENV variables to configure Arquillian > --------------------------------------------- > > Key: ARQ-1966 > URL: https://issues.jboss.org/browse/ARQ-1966 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.8.Final > Reporter: Aslak Knutsen > Fix For: 1.2.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 21:24:01 2015 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 28 Jul 2015 21:24:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1966) Support ENV variables to configure Arquillian In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1966: ---------------------------------- Summary: Support ENV variables to configure Arquillian Key: ARQ-1966 URL: https://issues.jboss.org/browse/ARQ-1966 Project: Arquillian Issue Type: Feature Request Components: Base Implementation Affects Versions: 1.1.8.Final Reporter: Aslak Knutsen Fix For: 1.2.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 21:33:01 2015 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 28 Jul 2015 21:33:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1966) Support ENV variables to configure Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1966: ------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Aslak Knutsen Resolution: Done Pushed upstream https://github.com/arquillian/arquillian-core/commit/8391d6960c138e16e9aed2fec407341f259f23da > Support ENV variables to configure Arquillian > --------------------------------------------- > > Key: ARQ-1966 > URL: https://issues.jboss.org/browse/ARQ-1966 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.8.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.2.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 21:39:01 2015 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 28 Jul 2015 21:39:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1967) Support 'alternative' deploy of ASM in Jacoco In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1967: ---------------------------------- Summary: Support 'alternative' deploy of ASM in Jacoco Key: ARQ-1967 URL: https://issues.jboss.org/browse/ARQ-1967 Project: Arquillian Issue Type: Feature Request Components: Extension - Jacoco Affects Versions: jacoco_1.0.0.Alpha8 Reporter: Aslak Knutsen -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 21:40:02 2015 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 28 Jul 2015 21:40:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1967) Support 'alternative' deploy of ASM in Jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1967: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-jacoco/pull/23 > Support 'alternative' deploy of ASM in Jacoco > ---------------------------------------------- > > Key: ARQ-1967 > URL: https://issues.jboss.org/browse/ARQ-1967 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha8 > Reporter: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 22:01:01 2015 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 28 Jul 2015 22:01:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1967) Support 'alternative' deploy of ASM in Jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1967: ------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Aslak Knutsen Fix Version/s: jacoco_1.0.0.next Resolution: Done pushed upstream https://github.com/arquillian/arquillian-extension-jacoco/commit/885dfd463f0f2f211c45ba9bf6cff4d1595a919e > Support 'alternative' deploy of ASM in Jacoco > ---------------------------------------------- > > Key: ARQ-1967 > URL: https://issues.jboss.org/browse/ARQ-1967 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha8 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: jacoco_1.0.0.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 23:12:02 2015 From: issues at jboss.org (Albert Wong (JIRA)) Date: Tue, 28 Jul 2015 23:12:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1968) Arquillian to fully support JBoss FUSE In-Reply-To: References: Message-ID: Albert Wong created ARQ-1968: -------------------------------- Summary: Arquillian to fully support JBoss FUSE Key: ARQ-1968 URL: https://issues.jboss.org/browse/ARQ-1968 Project: Arquillian Issue Type: Feature Request Components: OSGi Containers Affects Versions: 1.1.8.Final Reporter: Albert Wong Assignee: Thomas Diesler I have a customer that is interested in using Arquillian as their test framework for JBoss Fuse (all components). I understand that Pax Exam (https://access.redhat.com/solutions/1408033) is the officially supported test framework for Fuse. What would it take for Arquillian to be fully supported on Fuse? -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 29 04:05:02 2015 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 29 Jul 2015 04:05:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1968) Arquillian to fully support JBoss FUSE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-1968. --------------------------------- Resolution: Rejected We do this already for Fuse on Karaf (https://github.com/jboss-fuse/fabric8/blob/1.2.0.redhat-6-2-x-patch/itests/smoke/karaf/pom.xml#L67) Fuse on EAP is tested with no other, but Arquillian > Arquillian to fully support JBoss FUSE > -------------------------------------- > > Key: ARQ-1968 > URL: https://issues.jboss.org/browse/ARQ-1968 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Affects Versions: 1.1.8.Final > Reporter: Albert Wong > Assignee: Thomas Diesler > > I have a customer that is interested in using Arquillian as their test framework for JBoss Fuse (all components). I understand that Pax Exam (https://access.redhat.com/solutions/1408033) is the officially supported test framework for Fuse. What would it take for Arquillian to be fully supported on Fuse? -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 29 11:52:03 2015 From: issues at jboss.org (Albert Wong (JIRA)) Date: Wed, 29 Jul 2015 11:52:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1968) Arquillian to fully support JBoss FUSE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094014#comment-13094014 ] Albert Wong commented on ARQ-1968: ---------------------------------- So I don't quite understand. Are you saying that Arquillian already works for Fuse and it's just a matter of RH saying it's a tested framework like Arquillian on EAP (https://access.redhat.com/solutions/275433)? > Arquillian to fully support JBoss FUSE > -------------------------------------- > > Key: ARQ-1968 > URL: https://issues.jboss.org/browse/ARQ-1968 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Affects Versions: 1.1.8.Final > Reporter: Albert Wong > Assignee: Thomas Diesler > > I have a customer that is interested in using Arquillian as their test framework for JBoss Fuse (all components). I understand that Pax Exam (https://access.redhat.com/solutions/1408033) is the officially supported test framework for Fuse. What would it take for Arquillian to be fully supported on Fuse? -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 30 03:24:11 2015 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Thu, 30 Jul 2015 03:24:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1968) Arquillian to fully support JBoss FUSE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094130#comment-13094130 ] Thomas Diesler commented on ARQ-1968: ------------------------------------- I'm saying we already use Arquillian to test Fuse on Karaf as well as Fuse on EAP. Currently, the functionality in Arquillian covers all our use cases. If there should be a specific requirement/use case that is not covered, we can talk about the details of that. > Arquillian to fully support JBoss FUSE > -------------------------------------- > > Key: ARQ-1968 > URL: https://issues.jboss.org/browse/ARQ-1968 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Affects Versions: 1.1.8.Final > Reporter: Albert Wong > Assignee: Thomas Diesler > > I have a customer that is interested in using Arquillian as their test framework for JBoss Fuse (all components). I understand that Pax Exam (https://access.redhat.com/solutions/1408033) is the officially supported test framework for Fuse. What would it take for Arquillian to be fully supported on Fuse? -- This message was sent by Atlassian JIRA (v6.3.15#6346)