From issues at jboss.org  Tue Sep  5 11:48:02 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 5 Sep 2017 11:48:02 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2141) Update Selenium to 3.5.3
In-Reply-To: <JIRA.12710227.1504626435000@Atlassian.JIRA>
References: <JIRA.12710227.1504626435000@Atlassian.JIRA>
	<JIRA.12710227.1504626435977@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12710227.1504626435000.226477.1504626482235@Atlassian.JIRA>

Matous Jobanek created ARQ-2141:
-----------------------------------

             Summary: Update Selenium to 3.5.3
                 Key: ARQ-2141
                 URL: https://issues.jboss.org/browse/ARQ-2141
             Project: Arquillian
          Issue Type: Component Upgrade
          Components: Extension - Drone
    Affects Versions: drone_2.4.1
            Reporter: Matous Jobanek
            Assignee: Matous Jobanek
             Fix For: drone_2.4.2






--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Tue Sep  5 11:49:02 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 5 Sep 2017 11:49:02 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2141) Update Selenium to 3.5.3
In-Reply-To: <JIRA.12710227.1504626436000@Atlassian.JIRA>
References: <JIRA.12710227.1504626436000@Atlassian.JIRA>
	<JIRA.12710227.1504626436000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12710227.1504626436000.226517.1504626542591@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek updated ARQ-2141:
--------------------------------
    Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/111


> Update Selenium to 3.5.3
> ------------------------
>
>                 Key: ARQ-2141
>                 URL: https://issues.jboss.org/browse/ARQ-2141
>             Project: Arquillian
>          Issue Type: Component Upgrade
>          Components: Extension - Drone
>    Affects Versions: drone_2.4.1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.4.2
>
>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Tue Sep  5 14:30:00 2017
From: issues at jboss.org (Mark S (JIRA))
Date: Tue, 5 Sep 2017 14:30:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2142) TestNG - "unknown stack
 trace" on @Test( timeOut=10000)
In-Reply-To: <JIRA.12710255.1504636151000@Atlassian.JIRA>
References: <JIRA.12710255.1504636151000@Atlassian.JIRA>
	<JIRA.12710255.1504636151527@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12710255.1504636151000.227610.1504636200672@Atlassian.JIRA>

Mark S created ARQ-2142:
---------------------------

             Summary: TestNG - "unknown stack trace" on @Test( timeOut=10000)
                 Key: ARQ-2142
                 URL: https://issues.jboss.org/browse/ARQ-2142
             Project: Arquillian
          Issue Type: Bug
    Affects Versions: 1.1.13.Final, 1.1.12.Final
         Environment: * Windows 10
* Eclipse Oxygen
* Wildfly 10.1.0.Final
* Eclipse TestNG Plugin 6.11.0.201703011520
* https://github.com/ingwarsw/arquillian-suite-extension
            Reporter: Mark S


TestNG - "unknown stack trace" on @Test( timeOut=10000)

When setting a "org.testng.annotations.Test" annotation timeout value the following exception is output 
{code:java}
@Test( timeOut=10000)
    public void theTest() throws Exception
    {
        Assert.assertEquals( 1, 1 );
    }
{code}

{code}
14:16:27,461 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war")
Sep 05, 2017 2:16:28 PM org.jboss.arquillian.core.impl.ObserverImpl resolveArguments
WARNING: Argument 1 for UpdateTestResultBeforeAfter.update is null. It won't be invoked.
{code}

Maven POM depedencies
{code:xml}
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-depchain</artifactId>
      <version>2.2.4</version>
      <type>pom</type>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-api</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-impl-maven</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-api-maven</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-spi</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.arquillian.core</groupId>
      <artifactId>arquillian-core-api</artifactId>
      <version>1.1.13.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.wildfly</groupId>
      <artifactId>wildfly-arquillian-container-managed</artifactId>
      <version>8.2.1.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.arquillian.protocol</groupId>
      <artifactId>arquillian-protocol-servlet</artifactId>
      <version>1.1.13.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.arquillian.testng</groupId>
      <artifactId>arquillian-testng-container</artifactId>
      <version>1.1.13.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.eu.ingwar.tools</groupId>
      <artifactId>arquillian-suite-extension</artifactId>
      <version>1.1.4</version>
      <scope>test</scope>
    </dependency>
{code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Tue Sep  5 14:32:00 2017
From: issues at jboss.org (Mark S (JIRA))
Date: Tue, 5 Sep 2017 14:32:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2142) TestNG - "unknown stack
 trace" on @Test( timeOut=10000)
In-Reply-To: <JIRA.12710255.1504636152000@Atlassian.JIRA>
References: <JIRA.12710255.1504636152000@Atlassian.JIRA>
	<JIRA.12710255.1504636152000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12710255.1504636152000.227619.1504636320677@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark S updated ARQ-2142:
------------------------
    Description: 
TestNG - "unknown stack trace" on @Test( timeOut=10000)

When setting a "org.testng.annotations.Test" annotation timeout value the following exception is output 
{code:java}
@Test( timeOut=10000)
    public void theTest() throws Exception
    {
        Assert.assertEquals( 1, 1 );
    }
{code}

The only error logs before failure.
{code}
14:16:27,461 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war")
Sep 05, 2017 2:16:28 PM org.jboss.arquillian.core.impl.ObserverImpl resolveArguments
WARNING: Argument 1 for UpdateTestResultBeforeAfter.update is null. It won't be invoked.
FAILED: theTest

===============================================
    Default test
    Tests run: 1, Failures: 1, Skips: 0
===============================================

Sep 05, 2017 2:16:28 PM org.jboss.arquillian.core.impl.ObserverImpl resolveArguments
WARNING: Argument 2 for ArquillianServiceDeployer.undeploy is null. It won't be invoked.
14:16:28,472 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 92) WFLYUT0022: Unregistered web context: /test
{code}

Maven POM depedencies
{code:xml}
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-depchain</artifactId>
      <version>2.2.4</version>
      <type>pom</type>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-api</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-impl-maven</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-api-maven</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-spi</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.arquillian.core</groupId>
      <artifactId>arquillian-core-api</artifactId>
      <version>1.1.13.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.wildfly</groupId>
      <artifactId>wildfly-arquillian-container-managed</artifactId>
      <version>8.2.1.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.arquillian.protocol</groupId>
      <artifactId>arquillian-protocol-servlet</artifactId>
      <version>1.1.13.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.arquillian.testng</groupId>
      <artifactId>arquillian-testng-container</artifactId>
      <version>1.1.13.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.eu.ingwar.tools</groupId>
      <artifactId>arquillian-suite-extension</artifactId>
      <version>1.1.4</version>
      <scope>test</scope>
    </dependency>
{code}

  was:
TestNG - "unknown stack trace" on @Test( timeOut=10000)

When setting a "org.testng.annotations.Test" annotation timeout value the following exception is output 
{code:java}
@Test( timeOut=10000)
    public void theTest() throws Exception
    {
        Assert.assertEquals( 1, 1 );
    }
{code}

{code}
14:16:27,461 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war")
Sep 05, 2017 2:16:28 PM org.jboss.arquillian.core.impl.ObserverImpl resolveArguments
WARNING: Argument 1 for UpdateTestResultBeforeAfter.update is null. It won't be invoked.
{code}

Maven POM depedencies
{code:xml}
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-depchain</artifactId>
      <version>2.2.4</version>
      <type>pom</type>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-api</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-impl-maven</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-api-maven</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.shrinkwrap.resolver</groupId>
      <artifactId>shrinkwrap-resolver-spi</artifactId>
      <version>2.2.4</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.arquillian.core</groupId>
      <artifactId>arquillian-core-api</artifactId>
      <version>1.1.13.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.wildfly</groupId>
      <artifactId>wildfly-arquillian-container-managed</artifactId>
      <version>8.2.1.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.arquillian.protocol</groupId>
      <artifactId>arquillian-protocol-servlet</artifactId>
      <version>1.1.13.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.jboss.arquillian.testng</groupId>
      <artifactId>arquillian-testng-container</artifactId>
      <version>1.1.13.Final</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.eu.ingwar.tools</groupId>
      <artifactId>arquillian-suite-extension</artifactId>
      <version>1.1.4</version>
      <scope>test</scope>
    </dependency>
{code}



> TestNG - "unknown stack trace" on @Test( timeOut=10000)
> -------------------------------------------------------
>
>                 Key: ARQ-2142
>                 URL: https://issues.jboss.org/browse/ARQ-2142
>             Project: Arquillian
>          Issue Type: Bug
>    Affects Versions: 1.1.12.Final, 1.1.13.Final
>         Environment: * Windows 10
> * Eclipse Oxygen
> * Wildfly 10.1.0.Final
> * Eclipse TestNG Plugin 6.11.0.201703011520
> * https://github.com/ingwarsw/arquillian-suite-extension
>            Reporter: Mark S
>
> TestNG - "unknown stack trace" on @Test( timeOut=10000)
> When setting a "org.testng.annotations.Test" annotation timeout value the following exception is output 
> {code:java}
> @Test( timeOut=10000)
>     public void theTest() throws Exception
>     {
>         Assert.assertEquals( 1, 1 );
>     }
> {code}
> The only error logs before failure.
> {code}
> 14:16:27,461 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war")
> Sep 05, 2017 2:16:28 PM org.jboss.arquillian.core.impl.ObserverImpl resolveArguments
> WARNING: Argument 1 for UpdateTestResultBeforeAfter.update is null. It won't be invoked.
> FAILED: theTest
> ===============================================
>     Default test
>     Tests run: 1, Failures: 1, Skips: 0
> ===============================================
> Sep 05, 2017 2:16:28 PM org.jboss.arquillian.core.impl.ObserverImpl resolveArguments
> WARNING: Argument 2 for ArquillianServiceDeployer.undeploy is null. It won't be invoked.
> 14:16:28,472 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 92) WFLYUT0022: Unregistered web context: /test
> {code}
> Maven POM depedencies
> {code:xml}
>     <dependency>
>       <groupId>org.jboss.shrinkwrap.resolver</groupId>
>       <artifactId>shrinkwrap-resolver-depchain</artifactId>
>       <version>2.2.4</version>
>       <type>pom</type>
>       <scope>compile</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.shrinkwrap.resolver</groupId>
>       <artifactId>shrinkwrap-resolver-api</artifactId>
>       <version>2.2.4</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.shrinkwrap.resolver</groupId>
>       <artifactId>shrinkwrap-resolver-impl-maven</artifactId>
>       <version>2.2.4</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.shrinkwrap.resolver</groupId>
>       <artifactId>shrinkwrap-resolver-api-maven</artifactId>
>       <version>2.2.4</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.shrinkwrap.resolver</groupId>
>       <artifactId>shrinkwrap-resolver-spi</artifactId>
>       <version>2.2.4</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.arquillian.core</groupId>
>       <artifactId>arquillian-core-api</artifactId>
>       <version>1.1.13.Final</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.wildfly</groupId>
>       <artifactId>wildfly-arquillian-container-managed</artifactId>
>       <version>8.2.1.Final</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.arquillian.protocol</groupId>
>       <artifactId>arquillian-protocol-servlet</artifactId>
>       <version>1.1.13.Final</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.arquillian.testng</groupId>
>       <artifactId>arquillian-testng-container</artifactId>
>       <version>1.1.13.Final</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.eu.ingwar.tools</groupId>
>       <artifactId>arquillian-suite-extension</artifactId>
>       <version>1.1.4</version>
>       <scope>test</scope>
>     </dependency>
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Tue Sep  5 14:35:00 2017
From: issues at jboss.org (Mark S (JIRA))
Date: Tue, 5 Sep 2017 14:35:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2142) TestNG - "unknown stack
 trace" on @Test(timeOut=10000)
In-Reply-To: <JIRA.12710255.1504636152000@Atlassian.JIRA>
References: <JIRA.12710255.1504636152000@Atlassian.JIRA>
	<JIRA.12710255.1504636152000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12710255.1504636152000.227639.1504636500247@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark S updated ARQ-2142:
------------------------
    Summary: TestNG - "unknown stack trace" on @Test(timeOut=10000)  (was: TestNG - "unknown stack trace" on @Test( timeOut=10000))


> TestNG - "unknown stack trace" on @Test(timeOut=10000)
> ------------------------------------------------------
>
>                 Key: ARQ-2142
>                 URL: https://issues.jboss.org/browse/ARQ-2142
>             Project: Arquillian
>          Issue Type: Bug
>    Affects Versions: 1.1.12.Final, 1.1.13.Final
>         Environment: * Windows 10
> * Eclipse Oxygen
> * Wildfly 10.1.0.Final
> * Eclipse TestNG Plugin 6.11.0.201703011520
> * https://github.com/ingwarsw/arquillian-suite-extension
>            Reporter: Mark S
>
> TestNG - "unknown stack trace" on @Test( timeOut=10000)
> When setting a "org.testng.annotations.Test" annotation timeout value the following exception is output 
> {code:java}
> @Test( timeOut=10000)
>     public void theTest() throws Exception
>     {
>         Assert.assertEquals( 1, 1 );
>     }
> {code}
> The only error logs before failure.
> {code}
> 14:16:27,461 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war")
> Sep 05, 2017 2:16:28 PM org.jboss.arquillian.core.impl.ObserverImpl resolveArguments
> WARNING: Argument 1 for UpdateTestResultBeforeAfter.update is null. It won't be invoked.
> FAILED: theTest
> ===============================================
>     Default test
>     Tests run: 1, Failures: 1, Skips: 0
> ===============================================
> Sep 05, 2017 2:16:28 PM org.jboss.arquillian.core.impl.ObserverImpl resolveArguments
> WARNING: Argument 2 for ArquillianServiceDeployer.undeploy is null. It won't be invoked.
> 14:16:28,472 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 92) WFLYUT0022: Unregistered web context: /test
> {code}
> Maven POM depedencies
> {code:xml}
>     <dependency>
>       <groupId>org.jboss.shrinkwrap.resolver</groupId>
>       <artifactId>shrinkwrap-resolver-depchain</artifactId>
>       <version>2.2.4</version>
>       <type>pom</type>
>       <scope>compile</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.shrinkwrap.resolver</groupId>
>       <artifactId>shrinkwrap-resolver-api</artifactId>
>       <version>2.2.4</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.shrinkwrap.resolver</groupId>
>       <artifactId>shrinkwrap-resolver-impl-maven</artifactId>
>       <version>2.2.4</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.shrinkwrap.resolver</groupId>
>       <artifactId>shrinkwrap-resolver-api-maven</artifactId>
>       <version>2.2.4</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.shrinkwrap.resolver</groupId>
>       <artifactId>shrinkwrap-resolver-spi</artifactId>
>       <version>2.2.4</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.arquillian.core</groupId>
>       <artifactId>arquillian-core-api</artifactId>
>       <version>1.1.13.Final</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.wildfly</groupId>
>       <artifactId>wildfly-arquillian-container-managed</artifactId>
>       <version>8.2.1.Final</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.arquillian.protocol</groupId>
>       <artifactId>arquillian-protocol-servlet</artifactId>
>       <version>1.1.13.Final</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.jboss.arquillian.testng</groupId>
>       <artifactId>arquillian-testng-container</artifactId>
>       <version>1.1.13.Final</version>
>       <scope>test</scope>
>     </dependency>
>     <dependency>
>       <groupId>org.eu.ingwar.tools</groupId>
>       <artifactId>arquillian-suite-extension</artifactId>
>       <version>1.1.4</version>
>       <scope>test</scope>
>     </dependency>
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Sep  6 04:54:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 6 Sep 2017 04:54:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2140) Support for specifying
 the architecture for IE driver binary
In-Reply-To: <JIRA.12708943.1503912833000@Atlassian.JIRA>
References: <JIRA.12708943.1503912833000@Atlassian.JIRA>
	<JIRA.12708943.1503912833000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12708943.1503912833000.230424.1504688040696@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek updated ARQ-2140:
--------------------------------
    Fix Version/s: drone_2.4.2


> Support for specifying the architecture for IE driver binary
> ------------------------------------------------------------
>
>                 Key: ARQ-2140
>                 URL: https://issues.jboss.org/browse/ARQ-2140
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Extension - Drone
>            Reporter: Vaclav Muzikar
>             Fix For: drone_2.4.2
>
>
> When automatically downloading the IE driver binary, it should be possible to specify the target architecture.
> 64 bit version of the IE driver is having some issues with some IE versions, specifically the {{sendKeys}} method is very slow. Therefore it's recommended to use the 32 bit version of the driver.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Sep  6 04:54:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 6 Sep 2017 04:54:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2140) Support for specifying
 the architecture for IE driver binary
In-Reply-To: <JIRA.12708943.1503912833000@Atlassian.JIRA>
References: <JIRA.12708943.1503912833000@Atlassian.JIRA>
	<JIRA.12708943.1503912833000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12708943.1503912833000.230427.1504688040836@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek reassigned ARQ-2140:
-----------------------------------

    Assignee: Vaclav Muzikar


> Support for specifying the architecture for IE driver binary
> ------------------------------------------------------------
>
>                 Key: ARQ-2140
>                 URL: https://issues.jboss.org/browse/ARQ-2140
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Extension - Drone
>            Reporter: Vaclav Muzikar
>            Assignee: Vaclav Muzikar
>             Fix For: drone_2.4.2
>
>
> When automatically downloading the IE driver binary, it should be possible to specify the target architecture.
> 64 bit version of the IE driver is having some issues with some IE versions, specifically the {{sendKeys}} method is very slow. Therefore it's recommended to use the 32 bit version of the driver.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Sep  6 04:55:01 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 6 Sep 2017 04:55:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2140) Support for specifying
 the architecture for IE driver binary
In-Reply-To: <JIRA.12708943.1503912833000@Atlassian.JIRA>
References: <JIRA.12708943.1503912833000@Atlassian.JIRA>
	<JIRA.12708943.1503912833000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12708943.1503912833000.230436.1504688101441@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek closed ARQ-2140.
-------------------------------
    Resolution: Done


Pushed upstream in: https://github.com/arquillian/arquillian-extension-drone/commit/354360df2b616593fed3c7ea56282c48d1f5c837
Thank you [~vmuzikar]

> Support for specifying the architecture for IE driver binary
> ------------------------------------------------------------
>
>                 Key: ARQ-2140
>                 URL: https://issues.jboss.org/browse/ARQ-2140
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Extension - Drone
>            Reporter: Vaclav Muzikar
>            Assignee: Vaclav Muzikar
>             Fix For: drone_2.4.2
>
>
> When automatically downloading the IE driver binary, it should be possible to specify the target architecture.
> 64 bit version of the IE driver is having some issues with some IE versions, specifically the {{sendKeys}} method is very slow. Therefore it's recommended to use the 32 bit version of the driver.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Sep  6 04:55:01 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 6 Sep 2017 04:55:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2141) Update Selenium to 3.5.3
In-Reply-To: <JIRA.12710227.1504626436000@Atlassian.JIRA>
References: <JIRA.12710227.1504626436000@Atlassian.JIRA>
	<JIRA.12710227.1504626436000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12710227.1504626436000.230444.1504688101870@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek closed ARQ-2141.
-------------------------------
    Resolution: Done


> Update Selenium to 3.5.3
> ------------------------
>
>                 Key: ARQ-2141
>                 URL: https://issues.jboss.org/browse/ARQ-2141
>             Project: Arquillian
>          Issue Type: Component Upgrade
>          Components: Extension - Drone
>    Affects Versions: drone_2.4.1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.4.2
>
>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Mon Sep 11 04:53:00 2017
From: issues at jboss.org (Vlastislav Ramik (JIRA))
Date: Mon, 11 Sep 2017 04:53:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2130) Unaccessible
	arquillian-was-remote-8.5
In-Reply-To: <JIRA.12704621.1500988829000@Atlassian.JIRA>
References: <JIRA.12704621.1500988829000@Atlassian.JIRA>
	<JIRA.12704621.1500988829000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12704621.1500988829000.2089.1505119980419@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461755#comment-13461755 ] 

Vlastislav Ramik commented on ARQ-2130:
---------------------------------------

Hi [~gpoul], sorry for late answer. I guess it'd make sense to document this in the documentation. But for me it is not necessary any more. 

Btw. I've forked [1] the project and adapted for my use case, if you want you can take a look and if there is something what could have a value for the upstream, I can create a PR with whatever ;) I have in mind particularly the way how ibm dependencies are managed [2]. 

[1] https://github.com/vramik/arquillian-container-was/
[2] https://github.com/vramik/arquillian-container-was/commit/4bad4d5fd0910cd000d9f83321c498688507635e#diff-2077c186c52b32c5a5a0b0c61f5f1c6b

> Unaccessible arquillian-was-remote-8.5
> --------------------------------------
>
>                 Key: ARQ-2130
>                 URL: https://issues.jboss.org/browse/ARQ-2130
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: WebSphere Containers
>    Affects Versions: was_1.0.0.Beta2
>            Reporter: Vlastislav Ramik
>            Assignee: Gerhard Poul
>            Priority: Critical
>
> I'm not able to get 
> {noformat} 
> <groupId>org.jboss.arquillian.container</groupId>
> <artifactId>arquillian-was-remote-8.5</artifactId>
> <version>1.0.0.Beta2</version>
> {noformat}
> It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xml#L79-L88



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Mon Sep 11 12:04:00 2017
From: issues at jboss.org (Gerhard Poul (JIRA))
Date: Mon, 11 Sep 2017 12:04:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2130) Unaccessible
	arquillian-was-remote-8.5
In-Reply-To: <JIRA.12704621.1500988829000@Atlassian.JIRA>
References: <JIRA.12704621.1500988829000@Atlassian.JIRA>
	<JIRA.12704621.1500988829000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12704621.1500988829000.7154.1505145840619@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462238#comment-13462238 ] 

Gerhard Poul commented on ARQ-2130:
-----------------------------------

[~vramik] Similar to what you did in [2] there are official install artifacts from IBM that install the JARs available at http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/maven/repository/com/ibm/tools/target/was.installer/8.5.5/was.installer-8.5.5.pom but I decided against using them as we need the admin.client and jgss-provider, both of which are not on the official list provided by IBM, so it would be hit and miss whether they would work for anyone and would just require an additional step as well.

I'll be more than happy to move over to these dependencies if someone can convince IBM to include those JARs on the official list as people using Rational Application Developer will already have them as well.

I've also updated the documentation and I hope this makes it clearer that at this point in time the environment variables are required during runtime as well.

> Unaccessible arquillian-was-remote-8.5
> --------------------------------------
>
>                 Key: ARQ-2130
>                 URL: https://issues.jboss.org/browse/ARQ-2130
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: WebSphere Containers
>    Affects Versions: was_1.0.0.Beta2
>            Reporter: Vlastislav Ramik
>            Assignee: Gerhard Poul
>            Priority: Critical
>
> I'm not able to get 
> {noformat} 
> <groupId>org.jboss.arquillian.container</groupId>
> <artifactId>arquillian-was-remote-8.5</artifactId>
> <version>1.0.0.Beta2</version>
> {noformat}
> It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xml#L79-L88



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Sat Sep 16 22:25:00 2017
From: issues at jboss.org (John Ament (JIRA))
Date: Sat, 16 Sep 2017 22:25:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2143) Deployments that expect
 exceptions are not testable.
In-Reply-To: <JIRA.12712029.1505615056000@Atlassian.JIRA>
References: <JIRA.12712029.1505615056000@Atlassian.JIRA>
	<JIRA.12712029.1505615056869@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712029.1505615056000.38925.1505615100145@Atlassian.JIRA>

John Ament created ARQ-2143:
-------------------------------

             Summary: Deployments that expect exceptions are not testable.
                 Key: ARQ-2143
                 URL: https://issues.jboss.org/browse/ARQ-2143
             Project: Arquillian
          Issue Type: Bug
            Reporter: John Ament


Microprofile has some spec tests that rely on throwing exceptions on deployment.  https://github.com/eclipse/microprofile-jwt-auth/blob/master/tck/src/test/java/org/eclipse/microprofile/jwt/tck/container/jaxrs/AppScopedTest.java#L45 is one such test (ignore that it doesn't extend Arquillian).

The problem is that its not the code in the package that generates the exception, but classes added via an ArchiveProcessor, e.g. a CDI extension, that will generate the exception.  

I'm not sure the reasoning behind this behavior, but I don't see why {{ShouldThrowException}} implies that an archive is not testable.  Can this behavior be changed?



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Sep 20 20:11:00 2017
From: issues at jboss.org (Scott Stark (JIRA))
Date: Wed, 20 Sep 2017 20:11:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2144) arquillian-testng.jar
 is missing majority of TestNG classes in Wildfly-Swarm remote test
In-Reply-To: <JIRA.12712650.1505952619000@Atlassian.JIRA>
References: <JIRA.12712650.1505952619000@Atlassian.JIRA>
	<JIRA.12712650.1505952619793@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712650.1505952619000.57812.1505952660209@Atlassian.JIRA>

Scott Stark created ARQ-2144:
--------------------------------

             Summary: arquillian-testng.jar is missing majority of TestNG classes in Wildfly-Swarm remote test
                 Key: ARQ-2144
                 URL: https://issues.jboss.org/browse/ARQ-2144
             Project: Arquillian
          Issue Type: Bug
          Components: Base Implementation, Daemon
    Affects Versions: 1.1.13.Final
         Environment: jdk1.8.0_141 OSX
            Reporter: Scott Stark
            Assignee: Andrew Rubinger


I have created a simple cdi test that illustrates a problem I'm seeing with TestNG based remote tests running in Wildfly-Swarm. The issue is that the arquillian-testng.jar that is attached to the test WebArchive is missing the majority of TestNG classes, and so the test fails to load in the container runtime.

I have created a https://github.com/starksm64/arq-testnq-tests repository with two tests that illustrate the problem.

There is a ex.ExceptionTest that illustrates the inability to deploy the test due to NoClassDefFoundError:

{noformat}
2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) java.lang.NoClassDefFoundError: Failed to link ex/ExceptionTest (Module "deployment.exTest.war:main" from Service Module Loader): Failed to link org/jboss/arquillian/testng/Arquillian (Module "deployment.exTest.war:main" from Service Module Loader): Failed to link org/testng/IHookable (Module "deployment.exTest.war:main" from Service Module Loader): org/testng/ITestNGListener
2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:446)
2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:274)
2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:78)
2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.Module.loadModuleClass(Module.java:606)
2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363)
2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351)
2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.TestRunner.executeTest(TestRunner.java:45)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.server.Server.executeTest(Server.java:250)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.server.Server$StringCommandHandler.channelRead0(Server.java:361)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.server.Server$StringCommandHandler.channelRead0(Server.java:303)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:276)
2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:263)
2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
2017-09-20 16:49:37,564 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
2017-09-20 16:49:37,564 ERROR [stderr] (nioEventLoopGroup-3-1) 	at java.lang.Thread.run(Thread.java:748)

{noformat}

The test includes a TestNGArchiveProcessor AuxiliaryArchiveProcessor implementation that dumps out the arquillian-testng.jar seen in the WebArchive. It shows only the following org.testng package classes when run form within the Intellij IDEA IDE:


{noformat}
*-testng.jar contents: arquillian-testng.jar:
/org/
/org/testng/
/org/testng/IDEARemoteTestNG.class
/org/testng/IDEATestNGConfigurationListener.class
/org/testng/IDEATestNGInvokedMethodListener.class
/org/testng/IDEATestNGListener.class
/org/testng/IDEATestNGRemoteListener$DelegatedResult.class
/org/testng/IDEATestNGRemoteListener$ExposedTestResult.class
/org/testng/IDEATestNGRemoteListener.class
/org/testng/IDEATestNGSuiteListener.class
/org/testng/IDEATestNGTestListener.class
/org/testng/MapSerializerUtil$1.class
/org/testng/MapSerializerUtil$EscapeInfoProvider.class
/org/testng/MapSerializerUtil.class
/org/testng/RemoteTestNGStarter.class
/org/testng/TestNGExpectedPatterns.class
/org/testng/TestNGForkedSplitter.class
/org/testng/TestNGForkedStarter.class
/org/testng/TestNGTestDiscoveryListener.class
/org/testng/TestNGXmlSuiteHelper$Logger$1.class
/org/testng/TestNGXmlSuiteHelper$Logger.class
/org/testng/TestNGXmlSuiteHelper.class
{noformat}


When run from the command line the arquillian-testng.jar contains no org.testng package classes.

The underlying problem seems to be how the org.jboss.shrinkwrap.impl.base.URLPackageScanner includes package classes. I have a simple arq.URLPackageScannerTest in the  that illustrates how URLPackageScanner fails to located org.testng classes.





--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Sep 20 20:14:00 2017
From: issues at jboss.org (Scott Stark (JIRA))
Date: Wed, 20 Sep 2017 20:14:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2144) arquillian-testng.jar
 is missing majority of TestNG classes in Wildfly-Swarm remote test
In-Reply-To: <JIRA.12712650.1505952620000@Atlassian.JIRA>
References: <JIRA.12712650.1505952620000@Atlassian.JIRA>
	<JIRA.12712650.1505952620000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712650.1505952620000.57815.1505952840386@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Stark updated ARQ-2144:
-----------------------------
    Attachment: TestNGWorkaround.java


> arquillian-testng.jar is missing majority of TestNG classes in Wildfly-Swarm remote test
> ----------------------------------------------------------------------------------------
>
>                 Key: ARQ-2144
>                 URL: https://issues.jboss.org/browse/ARQ-2144
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Base Implementation, Daemon
>    Affects Versions: 1.1.13.Final
>         Environment: jdk1.8.0_141 OSX
>            Reporter: Scott Stark
>            Assignee: Andrew Rubinger
>         Attachments: TestNGWorkaround.java
>
>
> I have created a simple cdi test that illustrates a problem I'm seeing with TestNG based remote tests running in Wildfly-Swarm. The issue is that the arquillian-testng.jar that is attached to the test WebArchive is missing the majority of TestNG classes, and so the test fails to load in the container runtime.
> I have created a https://github.com/starksm64/arq-testnq-tests repository with two tests that illustrate the problem.
> There is a ex.ExceptionTest that illustrates the inability to deploy the test due to NoClassDefFoundError:
> {noformat}
> 2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) java.lang.NoClassDefFoundError: Failed to link ex/ExceptionTest (Module "deployment.exTest.war:main" from Service Module Loader): Failed to link org/jboss/arquillian/testng/Arquillian (Module "deployment.exTest.war:main" from Service Module Loader): Failed to link org/testng/IHookable (Module "deployment.exTest.war:main" from Service Module Loader): org/testng/ITestNGListener
> 2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:446)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:274)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:78)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.Module.loadModuleClass(Module.java:606)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.TestRunner.executeTest(TestRunner.java:45)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.server.Server.executeTest(Server.java:250)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.server.Server$StringCommandHandler.channelRead0(Server.java:361)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.server.Server$StringCommandHandler.channelRead0(Server.java:303)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:276)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:263)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
> 2017-09-20 16:49:37,564 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
> 2017-09-20 16:49:37,564 ERROR [stderr] (nioEventLoopGroup-3-1) 	at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The test includes a TestNGArchiveProcessor AuxiliaryArchiveProcessor implementation that dumps out the arquillian-testng.jar seen in the WebArchive. It shows only the following org.testng package classes when run form within the Intellij IDEA IDE:
> {noformat}
> *-testng.jar contents: arquillian-testng.jar:
> /org/
> /org/testng/
> /org/testng/IDEARemoteTestNG.class
> /org/testng/IDEATestNGConfigurationListener.class
> /org/testng/IDEATestNGInvokedMethodListener.class
> /org/testng/IDEATestNGListener.class
> /org/testng/IDEATestNGRemoteListener$DelegatedResult.class
> /org/testng/IDEATestNGRemoteListener$ExposedTestResult.class
> /org/testng/IDEATestNGRemoteListener.class
> /org/testng/IDEATestNGSuiteListener.class
> /org/testng/IDEATestNGTestListener.class
> /org/testng/MapSerializerUtil$1.class
> /org/testng/MapSerializerUtil$EscapeInfoProvider.class
> /org/testng/MapSerializerUtil.class
> /org/testng/RemoteTestNGStarter.class
> /org/testng/TestNGExpectedPatterns.class
> /org/testng/TestNGForkedSplitter.class
> /org/testng/TestNGForkedStarter.class
> /org/testng/TestNGTestDiscoveryListener.class
> /org/testng/TestNGXmlSuiteHelper$Logger$1.class
> /org/testng/TestNGXmlSuiteHelper$Logger.class
> /org/testng/TestNGXmlSuiteHelper.class
> {noformat}
> When run from the command line the arquillian-testng.jar contains no org.testng package classes.
> The underlying problem seems to be how the org.jboss.shrinkwrap.impl.base.URLPackageScanner includes package classes. I have a simple arq.URLPackageScannerTest in the  that illustrates how URLPackageScanner fails to located org.testng classes.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Sep 20 20:15:00 2017
From: issues at jboss.org (Scott Stark (JIRA))
Date: Wed, 20 Sep 2017 20:15:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2144) arquillian-testng.jar
 is missing majority of TestNG classes in Wildfly-Swarm remote test
In-Reply-To: <JIRA.12712650.1505952620000@Atlassian.JIRA>
References: <JIRA.12712650.1505952620000@Atlassian.JIRA>
	<JIRA.12712650.1505952620000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712650.1505952620000.57818.1505952900607@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466572#comment-13466572 ] 

Scott Stark commented on ARQ-2144:
----------------------------------

The TestNGWorkaround attachment is an example AuxiliaryArchiveAppender that I can use to include the required org.testng classes in order to run the test under Wildfly-Swarm without the class loading failures.


> arquillian-testng.jar is missing majority of TestNG classes in Wildfly-Swarm remote test
> ----------------------------------------------------------------------------------------
>
>                 Key: ARQ-2144
>                 URL: https://issues.jboss.org/browse/ARQ-2144
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Base Implementation, Daemon
>    Affects Versions: 1.1.13.Final
>         Environment: jdk1.8.0_141 OSX
>            Reporter: Scott Stark
>            Assignee: Andrew Rubinger
>         Attachments: TestNGWorkaround.java
>
>
> I have created a simple cdi test that illustrates a problem I'm seeing with TestNG based remote tests running in Wildfly-Swarm. The issue is that the arquillian-testng.jar that is attached to the test WebArchive is missing the majority of TestNG classes, and so the test fails to load in the container runtime.
> I have created a https://github.com/starksm64/arq-testnq-tests repository with two tests that illustrate the problem.
> There is a ex.ExceptionTest that illustrates the inability to deploy the test due to NoClassDefFoundError:
> {noformat}
> 2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) java.lang.NoClassDefFoundError: Failed to link ex/ExceptionTest (Module "deployment.exTest.war:main" from Service Module Loader): Failed to link org/jboss/arquillian/testng/Arquillian (Module "deployment.exTest.war:main" from Service Module Loader): Failed to link org/testng/IHookable (Module "deployment.exTest.war:main" from Service Module Loader): org/testng/ITestNGListener
> 2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 2017-09-20 16:49:37,560 ERROR [stderr] (nioEventLoopGroup-3-1) 	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:446)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:274)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:78)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.Module.loadModuleClass(Module.java:606)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351)
> 2017-09-20 16:49:37,561 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.TestRunner.executeTest(TestRunner.java:45)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.server.Server.executeTest(Server.java:250)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.server.Server$StringCommandHandler.channelRead0(Server.java:361)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at org.wildfly.swarm.arquillian.daemon.server.Server$StringCommandHandler.channelRead0(Server.java:303)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:276)
> 2017-09-20 16:49:37,562 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:263)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
> 2017-09-20 16:49:37,563 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
> 2017-09-20 16:49:37,564 ERROR [stderr] (nioEventLoopGroup-3-1) 	at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
> 2017-09-20 16:49:37,564 ERROR [stderr] (nioEventLoopGroup-3-1) 	at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The test includes a TestNGArchiveProcessor AuxiliaryArchiveProcessor implementation that dumps out the arquillian-testng.jar seen in the WebArchive. It shows only the following org.testng package classes when run form within the Intellij IDEA IDE:
> {noformat}
> *-testng.jar contents: arquillian-testng.jar:
> /org/
> /org/testng/
> /org/testng/IDEARemoteTestNG.class
> /org/testng/IDEATestNGConfigurationListener.class
> /org/testng/IDEATestNGInvokedMethodListener.class
> /org/testng/IDEATestNGListener.class
> /org/testng/IDEATestNGRemoteListener$DelegatedResult.class
> /org/testng/IDEATestNGRemoteListener$ExposedTestResult.class
> /org/testng/IDEATestNGRemoteListener.class
> /org/testng/IDEATestNGSuiteListener.class
> /org/testng/IDEATestNGTestListener.class
> /org/testng/MapSerializerUtil$1.class
> /org/testng/MapSerializerUtil$EscapeInfoProvider.class
> /org/testng/MapSerializerUtil.class
> /org/testng/RemoteTestNGStarter.class
> /org/testng/TestNGExpectedPatterns.class
> /org/testng/TestNGForkedSplitter.class
> /org/testng/TestNGForkedStarter.class
> /org/testng/TestNGTestDiscoveryListener.class
> /org/testng/TestNGXmlSuiteHelper$Logger$1.class
> /org/testng/TestNGXmlSuiteHelper$Logger.class
> /org/testng/TestNGXmlSuiteHelper.class
> {noformat}
> When run from the command line the arquillian-testng.jar contains no org.testng package classes.
> The underlying problem seems to be how the org.jboss.shrinkwrap.impl.base.URLPackageScanner includes package classes. I have a simple arq.URLPackageScannerTest in the  that illustrates how URLPackageScanner fails to located org.testng classes.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Sep 21 07:41:00 2017
From: issues at jboss.org (Ankit Ojha (JIRA))
Date: Thu, 21 Sep 2017 07:41:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2145) Unable to pass
 DesiredCapabilities from arquillian.xml with selenium grid
In-Reply-To: <JIRA.12712725.1505994016000@Atlassian.JIRA>
References: <JIRA.12712725.1505994016000@Atlassian.JIRA>
	<JIRA.12712725.1505994016937@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712725.1505994016000.60284.1505994060488@Atlassian.JIRA>

Ankit Ojha created ARQ-2145:
-------------------------------

             Summary: Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
                 Key: ARQ-2145
                 URL: https://issues.jboss.org/browse/ARQ-2145
             Project: Arquillian
          Issue Type: Bug
          Components: Configuration
         Environment: OS:Windows
Browser:Chrome
            Reporter: Ankit Ojha
         Attachments: image-2017-09-21-17-10-11-058.png

Unable to pass DesiredCapabilities from arquillian.xml with selenium grid

+Arquillian.xml+
{noformat}
<property name="remoteAddress">${gridhubaddress}</property>
	<property name="remote">true</property>
	<property name="chromePrintOptions">true</property>
	<property name="chromeArguments">-start-maximized</property>	
		<property name="chromeExperimentalOption">	
	{
  "prefs": {
    "download.default_directory": "${downloadlocation}"
	}
	}
</property>
{noformat}


 !image-2017-09-21-17-10-11-058.png|thumbnail! 






--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Sep 21 07:44:00 2017
From: issues at jboss.org (Ankit Ojha (JIRA))
Date: Thu, 21 Sep 2017 07:44:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2145) Unable to pass
 DesiredCapabilities from arquillian.xml with selenium grid
In-Reply-To: <JIRA.12712725.1505994017000@Atlassian.JIRA>
References: <JIRA.12712725.1505994017000@Atlassian.JIRA>
	<JIRA.12712725.1505994017000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712725.1505994017000.60298.1505994240286@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ankit Ojha updated ARQ-2145:
----------------------------
    Description: 
Unable to pass DesiredCapabilities from arquillian.xml with selenium grid

+Arquillian.xml+
{noformat}
<property name="remoteAddress">${gridhubaddress}</property>
	<property name="remote">true</property>
	<property name="chromePrintOptions">true</property>
	<property name="chromeArguments">-start-maximized</property>	
		<property name="chromeExperimentalOption">	
	{
  "prefs": {
    "download.default_directory": "${downloadlocation}"
	}
	}
</property>
{noformat}

*+Note+*
- Desired Capabilities were captured and worked as expected when executed without selenium grid
- Debugging with Remote WebDriver shows 
 !image-2017-09-21-17-10-11-058.png|thumbnail! 
- Initially my thought was <property name="chromeExperimentalOption"> had an issue but when i added<property name="chromeArguments">-start-maximized</property> , it did not worked as well. Without Grid both worked.





  was:
Unable to pass DesiredCapabilities from arquillian.xml with selenium grid

+Arquillian.xml+
{noformat}
<property name="remoteAddress">${gridhubaddress}</property>
	<property name="remote">true</property>
	<property name="chromePrintOptions">true</property>
	<property name="chromeArguments">-start-maximized</property>	
		<property name="chromeExperimentalOption">	
	{
  "prefs": {
    "download.default_directory": "${downloadlocation}"
	}
	}
</property>
{noformat}


 !image-2017-09-21-17-10-11-058.png|thumbnail! 






> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> -------------------------------------------------------------------------
>
>                 Key: ARQ-2145
>                 URL: https://issues.jboss.org/browse/ARQ-2145
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Configuration
>         Environment: OS:Windows
> Browser:Chrome
>            Reporter: Ankit Ojha
>         Attachments: image-2017-09-21-17-10-11-058.png
>
>
> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> +Arquillian.xml+
> {noformat}
> <property name="remoteAddress">${gridhubaddress}</property>
> 	<property name="remote">true</property>
> 	<property name="chromePrintOptions">true</property>
> 	<property name="chromeArguments">-start-maximized</property>	
> 		<property name="chromeExperimentalOption">	
> 	{
>   "prefs": {
>     "download.default_directory": "${downloadlocation}"
> 	}
> 	}
> </property>
> {noformat}
> *+Note+*
> - Desired Capabilities were captured and worked as expected when executed without selenium grid
> - Debugging with Remote WebDriver shows 
>  !image-2017-09-21-17-10-11-058.png|thumbnail! 
> - Initially my thought was <property name="chromeExperimentalOption"> had an issue but when i added<property name="chromeArguments">-start-maximized</property> , it did not worked as well. Without Grid both worked.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Sep 21 07:45:00 2017
From: issues at jboss.org (Ankit Ojha (JIRA))
Date: Thu, 21 Sep 2017 07:45:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2145) Unable to pass
 DesiredCapabilities from arquillian.xml with selenium grid
In-Reply-To: <JIRA.12712725.1505994017000@Atlassian.JIRA>
References: <JIRA.12712725.1505994017000@Atlassian.JIRA>
	<JIRA.12712725.1505994017000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712725.1505994017000.60300.1505994300351@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ankit Ojha updated ARQ-2145:
----------------------------
    Description: 
Unable to pass DesiredCapabilities from arquillian.xml with selenium grid

+Arquillian.xml+
{noformat}
<property name="remoteAddress">${gridhubaddress}</property>
	<property name="remote">true</property>
	<property name="chromePrintOptions">true</property>
	<property name="chromeArguments">-start-maximized</property>	
		<property name="chromeExperimentalOption">	
	{
  "prefs": {
    "download.default_directory": "${downloadlocation}"
	}
	}
</property>
{noformat}

*+Note+*
- Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
- Debugging with Remote WebDriver shows 
 !image-2017-09-21-17-10-11-058.png|thumbnail! 
- Initially my thought was <property name="chromeExperimentalOption"> had an issue but when i added<property name="chromeArguments">-start-maximized</property> , it did not worked as well. Without Grid both worked.





  was:
Unable to pass DesiredCapabilities from arquillian.xml with selenium grid

+Arquillian.xml+
{noformat}
<property name="remoteAddress">${gridhubaddress}</property>
	<property name="remote">true</property>
	<property name="chromePrintOptions">true</property>
	<property name="chromeArguments">-start-maximized</property>	
		<property name="chromeExperimentalOption">	
	{
  "prefs": {
    "download.default_directory": "${downloadlocation}"
	}
	}
</property>
{noformat}

*+Note+*
- Desired Capabilities were captured and worked as expected when executed without selenium grid
- Debugging with Remote WebDriver shows 
 !image-2017-09-21-17-10-11-058.png|thumbnail! 
- Initially my thought was <property name="chromeExperimentalOption"> had an issue but when i added<property name="chromeArguments">-start-maximized</property> , it did not worked as well. Without Grid both worked.







> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> -------------------------------------------------------------------------
>
>                 Key: ARQ-2145
>                 URL: https://issues.jboss.org/browse/ARQ-2145
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Configuration
>         Environment: OS:Windows
> Browser:Chrome
>            Reporter: Ankit Ojha
>         Attachments: image-2017-09-21-17-10-11-058.png
>
>
> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> +Arquillian.xml+
> {noformat}
> <property name="remoteAddress">${gridhubaddress}</property>
> 	<property name="remote">true</property>
> 	<property name="chromePrintOptions">true</property>
> 	<property name="chromeArguments">-start-maximized</property>	
> 		<property name="chromeExperimentalOption">	
> 	{
>   "prefs": {
>     "download.default_directory": "${downloadlocation}"
> 	}
> 	}
> </property>
> {noformat}
> *+Note+*
> - Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
> - Debugging with Remote WebDriver shows 
>  !image-2017-09-21-17-10-11-058.png|thumbnail! 
> - Initially my thought was <property name="chromeExperimentalOption"> had an issue but when i added<property name="chromeArguments">-start-maximized</property> , it did not worked as well. Without Grid both worked.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Sep 21 07:46:00 2017
From: issues at jboss.org (Ankit Ojha (JIRA))
Date: Thu, 21 Sep 2017 07:46:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2145) Unable to pass
 DesiredCapabilities from arquillian.xml with selenium grid
In-Reply-To: <JIRA.12712725.1505994017000@Atlassian.JIRA>
References: <JIRA.12712725.1505994017000@Atlassian.JIRA>
	<JIRA.12712725.1505994017000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712725.1505994017000.60315.1505994360564@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ankit Ojha updated ARQ-2145:
----------------------------
    Description: 
Unable to pass DesiredCapabilities from arquillian.xml with selenium grid

+Arquillian.xml+
{noformat}
<property name="remoteAddress">${gridhubaddress}</property>
	<property name="remote">true</property>
	<property name="chromePrintOptions">true</property>
	<property name="chromeArguments">-start-maximized</property>	
		<property name="chromeExperimentalOption">	
	{
  "prefs": {
    "download.default_directory": "${downloadlocation}"
	}
	}
</property>
{noformat}

*+Note+*
- Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
- Debugging with Remote WebDriver showed that it has the expected DesiredCapabilities (check screen attached) but when the browser was launched, it was launched without capabilites
- Initially my thought was <property name="chromeExperimentalOption"> had an issue but when i added<property name="chromeArguments">-start-maximized</property> , it did not worked as well. Without Grid both worked.





  was:
Unable to pass DesiredCapabilities from arquillian.xml with selenium grid

+Arquillian.xml+
{noformat}
<property name="remoteAddress">${gridhubaddress}</property>
	<property name="remote">true</property>
	<property name="chromePrintOptions">true</property>
	<property name="chromeArguments">-start-maximized</property>	
		<property name="chromeExperimentalOption">	
	{
  "prefs": {
    "download.default_directory": "${downloadlocation}"
	}
	}
</property>
{noformat}

*+Note+*
- Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
- Debugging with Remote WebDriver shows 
 !image-2017-09-21-17-10-11-058.png|thumbnail! 
- Initially my thought was <property name="chromeExperimentalOption"> had an issue but when i added<property name="chromeArguments">-start-maximized</property> , it did not worked as well. Without Grid both worked.







> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> -------------------------------------------------------------------------
>
>                 Key: ARQ-2145
>                 URL: https://issues.jboss.org/browse/ARQ-2145
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Configuration
>         Environment: OS:Windows
> Browser:Chrome
>            Reporter: Ankit Ojha
>         Attachments: image-2017-09-21-17-10-11-058.png
>
>
> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> +Arquillian.xml+
> {noformat}
> <property name="remoteAddress">${gridhubaddress}</property>
> 	<property name="remote">true</property>
> 	<property name="chromePrintOptions">true</property>
> 	<property name="chromeArguments">-start-maximized</property>	
> 		<property name="chromeExperimentalOption">	
> 	{
>   "prefs": {
>     "download.default_directory": "${downloadlocation}"
> 	}
> 	}
> </property>
> {noformat}
> *+Note+*
> - Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
> - Debugging with Remote WebDriver showed that it has the expected DesiredCapabilities (check screen attached) but when the browser was launched, it was launched without capabilites
> - Initially my thought was <property name="chromeExperimentalOption"> had an issue but when i added<property name="chromeArguments">-start-maximized</property> , it did not worked as well. Without Grid both worked.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Sep 21 08:03:00 2017
From: issues at jboss.org (Ankit Ojha (JIRA))
Date: Thu, 21 Sep 2017 08:03:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2145) Unable to pass
 DesiredCapabilities from arquillian.xml with selenium grid
In-Reply-To: <JIRA.12712725.1505994017000@Atlassian.JIRA>
References: <JIRA.12712725.1505994017000@Atlassian.JIRA>
	<JIRA.12712725.1505994017000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712725.1505994017000.60539.1505995380378@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ankit Ojha updated ARQ-2145:
----------------------------
    Description: 
Unable to pass DesiredCapabilities from arquillian.xml with selenium grid

+Arquillian.xml+
{noformat}
<property name="remoteAddress">${gridhubaddress}</property>
	<property name="remote">true</property>
	<property name="chromePrintOptions">true</property>
	<property name="chromeArguments">-start-maximized</property>	
		<property name="chromeExperimentalOption">	
	{
  "prefs": {
    "download.default_directory": "${downloadlocation}"
	}
	}
</property>
{noformat}

*+Note+*
- Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
- Debugging with Remote WebDriver showed that it has the expected DesiredCapabilities (check screen attached) but when the browser was launched, it was launched without capabilites
- Initially my thought was 
{noformat}
<property name="chromeExperimentalOption">
{noformat}
 had an issue but when i added 
{noformat}
<property name="chromeArguments">-start-maximized</property>
{noformat}
 it did not worked as well. Without Grid both worked.





  was:
Unable to pass DesiredCapabilities from arquillian.xml with selenium grid

+Arquillian.xml+
{noformat}
<property name="remoteAddress">${gridhubaddress}</property>
	<property name="remote">true</property>
	<property name="chromePrintOptions">true</property>
	<property name="chromeArguments">-start-maximized</property>	
		<property name="chromeExperimentalOption">	
	{
  "prefs": {
    "download.default_directory": "${downloadlocation}"
	}
	}
</property>
{noformat}

*+Note+*
- Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
- Debugging with Remote WebDriver showed that it has the expected DesiredCapabilities (check screen attached) but when the browser was launched, it was launched without capabilites
- Initially my thought was <property name="chromeExperimentalOption"> had an issue but when i added<property name="chromeArguments">-start-maximized</property> , it did not worked as well. Without Grid both worked.







> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> -------------------------------------------------------------------------
>
>                 Key: ARQ-2145
>                 URL: https://issues.jboss.org/browse/ARQ-2145
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Configuration
>         Environment: OS:Windows
> Browser:Chrome
>            Reporter: Ankit Ojha
>         Attachments: image-2017-09-21-17-10-11-058.png
>
>
> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> +Arquillian.xml+
> {noformat}
> <property name="remoteAddress">${gridhubaddress}</property>
> 	<property name="remote">true</property>
> 	<property name="chromePrintOptions">true</property>
> 	<property name="chromeArguments">-start-maximized</property>	
> 		<property name="chromeExperimentalOption">	
> 	{
>   "prefs": {
>     "download.default_directory": "${downloadlocation}"
> 	}
> 	}
> </property>
> {noformat}
> *+Note+*
> - Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
> - Debugging with Remote WebDriver showed that it has the expected DesiredCapabilities (check screen attached) but when the browser was launched, it was launched without capabilites
> - Initially my thought was 
> {noformat}
> <property name="chromeExperimentalOption">
> {noformat}
>  had an issue but when i added 
> {noformat}
> <property name="chromeArguments">-start-maximized</property>
> {noformat}
>  it did not worked as well. Without Grid both worked.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Sep 21 11:29:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 21 Sep 2017 11:29:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2145) Unable to pass
 DesiredCapabilities from arquillian.xml with selenium grid
In-Reply-To: <JIRA.12712725.1505994017000@Atlassian.JIRA>
References: <JIRA.12712725.1505994017000@Atlassian.JIRA>
	<JIRA.12712725.1505994017000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712725.1505994017000.62565.1506007740429@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467008#comment-13467008 ] 

Matous Jobanek commented on ARQ-2145:
-------------------------------------

Hi, 
thanks for reporting.
Which version of Drone do you use?

> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> -------------------------------------------------------------------------
>
>                 Key: ARQ-2145
>                 URL: https://issues.jboss.org/browse/ARQ-2145
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Configuration
>         Environment: OS:Windows
> Browser:Chrome
>            Reporter: Ankit Ojha
>         Attachments: image-2017-09-21-17-10-11-058.png
>
>
> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> +Arquillian.xml+
> {noformat}
> <property name="remoteAddress">${gridhubaddress}</property>
> 	<property name="remote">true</property>
> 	<property name="chromePrintOptions">true</property>
> 	<property name="chromeArguments">-start-maximized</property>	
> 		<property name="chromeExperimentalOption">	
> 	{
>   "prefs": {
>     "download.default_directory": "${downloadlocation}"
> 	}
> 	}
> </property>
> {noformat}
> *+Note+*
> - Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
> - Debugging with Remote WebDriver showed that it has the expected DesiredCapabilities (check screen attached) but when the browser was launched, it was launched without capabilites
> - Initially my thought was 
> {noformat}
> <property name="chromeExperimentalOption">
> {noformat}
>  had an issue but when i added 
> {noformat}
> <property name="chromeArguments">-start-maximized</property>
> {noformat}
>  it did not worked as well. Without Grid both worked.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Sep 21 12:25:00 2017
From: issues at jboss.org (Ankit Ojha (JIRA))
Date: Thu, 21 Sep 2017 12:25:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2145) Unable to pass
 DesiredCapabilities from arquillian.xml with selenium grid
In-Reply-To: <JIRA.12712725.1505994017000@Atlassian.JIRA>
References: <JIRA.12712725.1505994017000@Atlassian.JIRA>
	<JIRA.12712725.1505994017000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712725.1505994017000.62816.1506011100345@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467044#comment-13467044 ] 

Ankit Ojha commented on ARQ-2145:
---------------------------------

We are using 
{noformat}
<arquillian-drone-bom.version>2.1.0.Alpha1</arquillian-drone-bom.version>
{noformat}

Our usecase is to set Desired Capabilities with selenium grid and eventually set default download location to a specific location.

As stated in the description, it works perfectly fine without selenium grid configuration.

> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> -------------------------------------------------------------------------
>
>                 Key: ARQ-2145
>                 URL: https://issues.jboss.org/browse/ARQ-2145
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Configuration
>         Environment: OS:Windows
> Browser:Chrome
>            Reporter: Ankit Ojha
>         Attachments: image-2017-09-21-17-10-11-058.png
>
>
> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> +Arquillian.xml+
> {noformat}
> <property name="remoteAddress">${gridhubaddress}</property>
> 	<property name="remote">true</property>
> 	<property name="chromePrintOptions">true</property>
> 	<property name="chromeArguments">-start-maximized</property>	
> 		<property name="chromeExperimentalOption">	
> 	{
>   "prefs": {
>     "download.default_directory": "${downloadlocation}"
> 	}
> 	}
> </property>
> {noformat}
> *+Note+*
> - Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
> - Debugging with Remote WebDriver showed that it has the expected DesiredCapabilities (check screen attached) but when the browser was launched, it was launched without capabilites
> - Initially my thought was 
> {noformat}
> <property name="chromeExperimentalOption">
> {noformat}
>  had an issue but when i added 
> {noformat}
> <property name="chromeArguments">-start-maximized</property>
> {noformat}
>  it did not worked as well. Without Grid both worked.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Sep 22 03:11:01 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Fri, 22 Sep 2017 03:11:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2145) Unable to pass
 DesiredCapabilities from arquillian.xml with selenium grid
In-Reply-To: <JIRA.12712725.1505994017000@Atlassian.JIRA>
References: <JIRA.12712725.1505994017000@Atlassian.JIRA>
	<JIRA.12712725.1505994017000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712725.1505994017000.64307.1506064261955@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467198#comment-13467198 ] 

Matous Jobanek commented on ARQ-2145:
-------------------------------------

Yeah,
please try to update to the latest version: {{2.4.2}} and check if you have still the same problem or if it is already fixed there.
In older versions of Drone, there was a problem with a proper setting of ChromeOptions for cases when selenium grid is used. In new versions (since 2.2.0) it should be fixed. Please give it with the latest one.


> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> -------------------------------------------------------------------------
>
>                 Key: ARQ-2145
>                 URL: https://issues.jboss.org/browse/ARQ-2145
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Configuration
>         Environment: OS:Windows
> Browser:Chrome
>            Reporter: Ankit Ojha
>         Attachments: image-2017-09-21-17-10-11-058.png
>
>
> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> +Arquillian.xml+
> {noformat}
> <property name="remoteAddress">${gridhubaddress}</property>
> 	<property name="remote">true</property>
> 	<property name="chromePrintOptions">true</property>
> 	<property name="chromeArguments">-start-maximized</property>	
> 		<property name="chromeExperimentalOption">	
> 	{
>   "prefs": {
>     "download.default_directory": "${downloadlocation}"
> 	}
> 	}
> </property>
> {noformat}
> *+Note+*
> - Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
> - Debugging with Remote WebDriver showed that it has the expected DesiredCapabilities (check screen attached) but when the browser was launched, it was launched without capabilites
> - Initially my thought was 
> {noformat}
> <property name="chromeExperimentalOption">
> {noformat}
>  had an issue but when i added 
> {noformat}
> <property name="chromeArguments">-start-maximized</property>
> {noformat}
>  it did not worked as well. Without Grid both worked.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Sep 22 08:05:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Fri, 22 Sep 2017 08:05:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2145) Unable to pass
 DesiredCapabilities from arquillian.xml with selenium grid
In-Reply-To: <JIRA.12712725.1505994017000@Atlassian.JIRA>
References: <JIRA.12712725.1505994017000@Atlassian.JIRA>
	<JIRA.12712725.1505994017000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712725.1505994017000.66540.1506081900607@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek reassigned ARQ-2145:
-----------------------------------

    Assignee: Matous Jobanek


> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> -------------------------------------------------------------------------
>
>                 Key: ARQ-2145
>                 URL: https://issues.jboss.org/browse/ARQ-2145
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Configuration
>         Environment: OS:Windows
> Browser:Chrome
>            Reporter: Ankit Ojha
>            Assignee: Matous Jobanek
>         Attachments: image-2017-09-21-17-10-11-058.png
>
>
> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> +Arquillian.xml+
> {noformat}
> <property name="remoteAddress">${gridhubaddress}</property>
> 	<property name="remote">true</property>
> 	<property name="chromePrintOptions">true</property>
> 	<property name="chromeArguments">-start-maximized</property>	
> 		<property name="chromeExperimentalOption">	
> 	{
>   "prefs": {
>     "download.default_directory": "${downloadlocation}"
> 	}
> 	}
> </property>
> {noformat}
> *+Note+*
> - Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
> - Debugging with Remote WebDriver showed that it has the expected DesiredCapabilities (check screen attached) but when the browser was launched, it was launched without capabilites
> - Initially my thought was 
> {noformat}
> <property name="chromeExperimentalOption">
> {noformat}
>  had an issue but when i added 
> {noformat}
> <property name="chromeArguments">-start-maximized</property>
> {noformat}
>  it did not worked as well. Without Grid both worked.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Sep 22 08:06:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Fri, 22 Sep 2017 08:06:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2145) Unable to pass
 DesiredCapabilities from arquillian.xml with selenium grid
In-Reply-To: <JIRA.12712725.1505994017000@Atlassian.JIRA>
References: <JIRA.12712725.1505994017000@Atlassian.JIRA>
	<JIRA.12712725.1505994017000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712725.1505994017000.66548.1506081960781@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek updated ARQ-2145:
--------------------------------
    Affects Version/s: drone_2.1.0.Alpha1


> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> -------------------------------------------------------------------------
>
>                 Key: ARQ-2145
>                 URL: https://issues.jboss.org/browse/ARQ-2145
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: drone_2.1.0.Alpha1
>         Environment: OS:Windows
> Browser:Chrome
>            Reporter: Ankit Ojha
>            Assignee: Matous Jobanek
>         Attachments: image-2017-09-21-17-10-11-058.png
>
>
> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> +Arquillian.xml+
> {noformat}
> <property name="remoteAddress">${gridhubaddress}</property>
> 	<property name="remote">true</property>
> 	<property name="chromePrintOptions">true</property>
> 	<property name="chromeArguments">-start-maximized</property>	
> 		<property name="chromeExperimentalOption">	
> 	{
>   "prefs": {
>     "download.default_directory": "${downloadlocation}"
> 	}
> 	}
> </property>
> {noformat}
> *+Note+*
> - Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
> - Debugging with Remote WebDriver showed that it has the expected DesiredCapabilities (check screen attached) but when the browser was launched, it was launched without capabilites
> - Initially my thought was 
> {noformat}
> <property name="chromeExperimentalOption">
> {noformat}
>  had an issue but when i added 
> {noformat}
> <property name="chromeArguments">-start-maximized</property>
> {noformat}
>  it did not worked as well. Without Grid both worked.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Sep 22 08:06:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Fri, 22 Sep 2017 08:06:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2145) Unable to pass
 DesiredCapabilities from arquillian.xml with selenium grid
In-Reply-To: <JIRA.12712725.1505994017000@Atlassian.JIRA>
References: <JIRA.12712725.1505994017000@Atlassian.JIRA>
	<JIRA.12712725.1505994017000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12712725.1505994017000.66555.1506081960997@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek updated ARQ-2145:
--------------------------------
    Component/s: Extension - Drone
                     (was: Configuration)


> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> -------------------------------------------------------------------------
>
>                 Key: ARQ-2145
>                 URL: https://issues.jboss.org/browse/ARQ-2145
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Drone
>    Affects Versions: drone_2.1.0.Alpha1
>         Environment: OS:Windows
> Browser:Chrome
>            Reporter: Ankit Ojha
>            Assignee: Matous Jobanek
>         Attachments: image-2017-09-21-17-10-11-058.png
>
>
> Unable to pass DesiredCapabilities from arquillian.xml with selenium grid
> +Arquillian.xml+
> {noformat}
> <property name="remoteAddress">${gridhubaddress}</property>
> 	<property name="remote">true</property>
> 	<property name="chromePrintOptions">true</property>
> 	<property name="chromeArguments">-start-maximized</property>	
> 		<property name="chromeExperimentalOption">	
> 	{
>   "prefs": {
>     "download.default_directory": "${downloadlocation}"
> 	}
> 	}
> </property>
> {noformat}
> *+Note+*
> - Desired Capabilities were captured and worked as expected when executed {color:red}without {color}selenium grid
> - Debugging with Remote WebDriver showed that it has the expected DesiredCapabilities (check screen attached) but when the browser was launched, it was launched without capabilites
> - Initially my thought was 
> {noformat}
> <property name="chromeExperimentalOption">
> {noformat}
>  had an issue but when i added 
> {noformat}
> <property name="chromeArguments">-start-maximized</property>
> {noformat}
>  it did not worked as well. Without Grid both worked.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Sun Sep 24 05:33:00 2017
From: issues at jboss.org (Rostislav Svoboda (JIRA))
Date: Sun, 24 Sep 2017 05:33:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2066) Support for JUnit 5
In-Reply-To: <JIRA.12667778.1481794982000@Atlassian.JIRA>
References: <JIRA.12667778.1481794982000@Atlassian.JIRA>
	<JIRA.12667778.1481794982000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12667778.1481794982000.69566.1506245580952@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467617#comment-13467617 ] 

Rostislav Svoboda commented on ARQ-2066:
----------------------------------------

Any update on this ?

JUnit 5 is out, https://developer.jboss.org/message/970675#970675 seems not working any more due to API changes.

> Support for JUnit 5
> -------------------
>
>                 Key: ARQ-2066
>                 URL: https://issues.jboss.org/browse/ARQ-2066
>             Project: Arquillian
>          Issue Type: Feature Request
>            Reporter: Tobias Stadler
>
> The final relase of JUnit 5 is scheduled for Q1 2017. It would be nice if Arquillian would support it then.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Sun Sep 24 08:00:01 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 24 Sep 2017 08:00:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2066) Support for JUnit 5
In-Reply-To: <JIRA.12667778.1481794982000@Atlassian.JIRA>
References: <JIRA.12667778.1481794982000@Atlassian.JIRA>
	<JIRA.12667778.1481794982000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12667778.1481794982000.69605.1506254401507@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467624#comment-13467624 ] 

Bartosz Majsak commented on ARQ-2066:
-------------------------------------

[~rsvoboda] would be awesome if you could help us make it work.

> Support for JUnit 5
> -------------------
>
>                 Key: ARQ-2066
>                 URL: https://issues.jboss.org/browse/ARQ-2066
>             Project: Arquillian
>          Issue Type: Feature Request
>            Reporter: Tobias Stadler
>
> The final relase of JUnit 5 is scheduled for Q1 2017. It would be nice if Arquillian would support it then.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Sep 28 09:33:02 2017
From: issues at jboss.org (S Haster (JIRA))
Date: Thu, 28 Sep 2017 09:33:02 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-512) ClassCastException
 while performing MouseActions against selenium 3.6.0
In-Reply-To: <JIRA.12713913.1506605534000@Atlassian.JIRA>
References: <JIRA.12713913.1506605534000@Atlassian.JIRA>
	<JIRA.12713913.1506605534711@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12713913.1506605534000.90781.1506605582767@Atlassian.JIRA>

S Haster created ARQGRA-512:
-------------------------------

             Summary: ClassCastException while performing MouseActions against selenium 3.6.0
                 Key: ARQGRA-512
                 URL: https://issues.jboss.org/browse/ARQGRA-512
             Project: Arquillian Graphene
          Issue Type: Bug
    Affects Versions: 2.3.1
            Reporter: S Haster


Selenium 3.6.0 is api breaking (w/ regards to 3.5.3) and graphene is not yet updated.

We recently upgraded to selenium 3.6.0 and are running graphene 2.3.1

While performing a ClickAndHoldAction we get a ClassCastException. The reason is because selenium-api created a second Locatable as a super-interface of the old one and GrapheneElementImpl uses the 'old' one but RemoteWebElement only implements the 'new' one. 

Stacktrace: 


{noformat}
java.lang.ClassCastException: org.openqa.selenium.remote.RemoteWebElement cannot be cast to org.openqa.selenium.internal.Locatable
	at org.jboss.arquillian.graphene.GrapheneElementImpl.getCoordinates(GrapheneElementImpl.java:259)
	at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:130)
	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:169)
	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:47)
	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:43)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96)
	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:43)
	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
	at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139)
	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
	at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50)
	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:241)
	at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62)
	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:237)
	at org.openqa.selenium.interactions.internal.MouseAction.getActionLocation(MouseAction.java:65)
	at org.openqa.selenium.interactions.internal.MouseAction.moveToLocation(MouseAction.java:72)
	at org.openqa.selenium.interactions.ClickAndHoldAction.perform(ClickAndHoldAction.java:45)
	at org.openqa.selenium.interactions.CompositeAction.perform(CompositeAction.java:36)
	at org.openqa.selenium.interactions.Actions$BuiltAction.perform(Actions.java:641)
	at nl.topicus.keyhub.arquillian.selenium.page.console.GMyGroupFoldersPage.dragOnto(GMyGroupFoldersPage.java:56)
      at <our testclass>
{noformat}

The 'dragOnto'method does:

{code:java}
public void dragOnto(String groupName, String folderName)
	{
		WebDriver driver = GrapheneHelper.getDriver(add);
		WebElement group = driver.findElement(
			By.cssSelector("div.content--part div.tasks .task[data-value='" + groupName + "']"));
		WebElement targetFolder = driver
			.findElement(By.cssSelector("div.content--part[data-value='" + folderName + "']"));
		Action dragAndDrop = new Actions(driver).dragAndDrop(group, targetFolder).build();
		dragAndDrop.perform();
	}
{code}










--
This message was sent by Atlassian JIRA
(v7.2.3#72005)