From issues at jboss.org Wed May 3 05:49:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 3 May 2017 05:49:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2108) Support for CouchDB seeding in standalone DSL In-Reply-To: References: Message-ID: Alex Soto created ARQ-2108: ------------------------------ Summary: Support for CouchDB seeding in standalone DSL Key: ARQ-2108 URL: https://issues.jboss.org/browse/ARQ-2108 Project: Arquillian Issue Type: Sub-task Reporter: Alex Soto -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 3 05:49:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 3 May 2017 05:49:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2108) Support for CouchDB seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto reassigned ARQ-2108: ------------------------------ Assignee: Alex Soto > Support for CouchDB seeding in standalone DSL > --------------------------------------------- > > Key: ARQ-2108 > URL: https://issues.jboss.org/browse/ARQ-2108 > Project: Arquillian > Issue Type: Sub-task > Reporter: Alex Soto > Assignee: Alex Soto > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 3 05:54:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 3 May 2017 05:54:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2108) Support for CouchDB seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-2108: --------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/78 > Support for CouchDB seeding in standalone DSL > --------------------------------------------- > > Key: ARQ-2108 > URL: https://issues.jboss.org/browse/ARQ-2108 > Project: Arquillian > Issue Type: Sub-task > Reporter: Alex Soto > Assignee: Alex Soto > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 3 05:54:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 3 May 2017 05:54:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2108) Support for CouchDB seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-2108: --------------------------- Component/s: Extension - Persistence > Support for CouchDB seeding in standalone DSL > --------------------------------------------- > > Key: ARQ-2108 > URL: https://issues.jboss.org/browse/ARQ-2108 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 3 05:56:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 3 May 2017 05:56:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2108) Support for CouchDB seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto resolved ARQ-2108. ---------------------------- Resolution: Done Upstream https://github.com/arquillian/arquillian-extension-persistence/commit/4ebdb2ffdb2623c303c15034f051d8de1c4b8ce8 > Support for CouchDB seeding in standalone DSL > --------------------------------------------- > > Key: ARQ-2108 > URL: https://issues.jboss.org/browse/ARQ-2108 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 4 11:09:00 2017 From: issues at jboss.org (Ladislav Thon (JIRA)) Date: Thu, 4 May 2017 11:09:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2109) EJBInjectionEnricher makes too strong assumptions about JNDI names in the "anonymous" case In-Reply-To: References: Message-ID: Ladislav Thon created ARQ-2109: ---------------------------------- Summary: EJBInjectionEnricher makes too strong assumptions about JNDI names in the "anonymous" case Key: ARQ-2109 URL: https://issues.jboss.org/browse/ARQ-2109 Project: Arquillian Issue Type: Bug Components: Runtime Enricher SPI Reporter: Ladislav Thon The {{EJBInjectionEnricher}} supports injecting the test instance fields annotated with {{javax.ejb.EJB}}. However, looking at the {{EJBInjectionEnricher.getJndiNamesForAnonymousEJB}} method, it makes too strong assumptions about the JNDI name. Specifically, it assumes the {{test.ear}} and {{test}} names. That doesn't necessarily have to be correct (e.g. WildFly Swarm Arquillian adapter doesn't use these names). There's an easy way to improve this for some situations: also consider the {{java:module}} portable namespace. It can't fix all situations, but it does fix some of them. (For Swarm, it's completely enough, since Swarm doesn't support EARs.) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 4 14:57:00 2017 From: issues at jboss.org (Derek Foster (JIRA)) Date: Thu, 4 May 2017 14:57:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2110) DBUnit Config allowEmptyFields In-Reply-To: References: Message-ID: Derek Foster created ARQ-2110: --------------------------------- Summary: DBUnit Config allowEmptyFields Key: ARQ-2110 URL: https://issues.jboss.org/browse/ARQ-2110 Project: Arquillian Issue Type: Feature Request Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha7 Reporter: Derek Foster Assignee: Bartosz Majsak The current version of the persistence extension is based on DbUnit 2.4.8, but since then DbUnit has updated to 2.5.3 which has included a feature of allowing empty fields, as opposed to forcing null fields in databases. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 4 14:58:00 2017 From: issues at jboss.org (Derek Foster (JIRA)) Date: Thu, 4 May 2017 14:58:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2110) DBUnit Config allowEmptyFields In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Foster updated ARQ-2110: ------------------------------ Description: The current version of the persistence extension is based on DbUnit 2.4.8, but since then DbUnit has updated to 2.5.3 which has included a feature of allowing empty fields, as opposed to forcing null fields in databases. This feature is quite useful for seeding data. (was: The current version of the persistence extension is based on DbUnit 2.4.8, but since then DbUnit has updated to 2.5.3 which has included a feature of allowing empty fields, as opposed to forcing null fields in databases.) > DBUnit Config allowEmptyFields > ------------------------------ > > Key: ARQ-2110 > URL: https://issues.jboss.org/browse/ARQ-2110 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Derek Foster > Assignee: Bartosz Majsak > > The current version of the persistence extension is based on DbUnit 2.4.8, but since then DbUnit has updated to 2.5.3 which has included a feature of allowing empty fields, as opposed to forcing null fields in databases. This feature is quite useful for seeding data. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 8 05:48:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Mon, 8 May 2017 05:48:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2086) Test failures not reported with recent versions of TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402929#comment-13402929 ] Dipak Pawar commented on ARQ-2086: ---------------------------------- Following are few findings for this: * All failed tests are passing? ** As in arquillian-core we are not setting status as failed when our test is failing, we are setting only throwable which is AssertionError in failed tests. ** This was working with previous version of testng as in previous version it's checking only exception thrown, not it's status. ** So to work with testng 6.11 we have to set status as failed with throwable. ** https://github.com/cbeust/testng/commit/8fba9498efaaec18ce23572fc5a95afb6d9554c3#diff-b3080bc9d91f177f63b5fd4d9c501364R1326 * Why new SkipExecption() is not able to skip tests in case of remote execution. ** If we have some tests as Skipped then in the result we are not setting it's throwable, we are setting only status as skipped, but after this testng is overriding it's status as success as it doesn't have throwable which is skipException here ** So to fix it set throwable even if test is skipping. ** https://github.com/dipak-pawar/arquillian-core/commit/d93431d38e18b2b54e9c17bd17c88adc0080c151#diff-4417a7a63a141484c8ecb8e3958a3924R64 * Root cause of failure of TestNGIntegrationTestCase is testng ** Look for fix https://github.com/cbeust/testng/pull/1427 All work is done look [here|https://github.com/dipak-pawar/arquillian-core/tree/testng_issue], waiting to merge upstream pr. Thanks, Dipak > Test failures not reported with recent versions of TestNG > --------------------------------------------------------- > > Key: ARQ-2086 > URL: https://issues.jboss.org/browse/ARQ-2086 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.12.Final > Reporter: Gunnar Morling > Assignee: Bartosz Majsak > Priority: Blocker > > When using recent TestNG versions (> 6.8.21) with Arquillian, failing tests are accidentally reported as passing. > A reproducer can be found at https://github.com/gunnarmorling/arquillian-testng-bug. > There is a single test which is expected to fail, but it actually is reported as successful with TestNG 6.11. It is reported as failed as expected with 6.8.21. Run {{mvn clean install}} for reproducing. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 8 05:49:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Mon, 8 May 2017 05:49:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2086) Test failures not reported with recent versions of TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402929#comment-13402929 ] Dipak Pawar edited comment on ARQ-2086 at 5/8/17 5:48 AM: ---------------------------------------------------------- Following are few findings for this: * All failed tests are passing? ** As in arquillian-core we are not setting status as failed when our test is failing, we are setting only throwable which is AssertionError in failed tests. ** This was working with previous version of testng as in previous version it's checking only exception thrown, not it's status. ** So to work with testng 6.11 we have to set status as failed with throwable. ** https://github.com/cbeust/testng/commit/8fba9498efaaec18ce23572fc5a95afb6d9554c3#diff-b3080bc9d91f177f63b5fd4d9c501364R1326 * Why new SkipExecption() is not able to skip tests in case of remote execution. ** If we have some tests as Skipped then in the result we are not setting it's throwable, we are setting only status as skipped, but after this testng is overriding it's status as success as it doesn't have throwable which is skipException here ** So to fix it set throwable even if test is skipping. ** https://github.com/dipak-pawar/arquillian-core/commit/d93431d38e18b2b54e9c17bd17c88adc0080c151#diff-4417a7a63a141484c8ecb8e3958a3924R64 * Root cause of failure of TestNGIntegrationTestCase is testng ** Look for fix https://github.com/cbeust/testng/pull/1427 All work is done, look [here|https://github.com/dipak-pawar/arquillian-core/tree/testng_issue], waiting to merge upstream pr. Thanks, Dipak was (Author: dipakpawar231): Following are few findings for this: * All failed tests are passing? ** As in arquillian-core we are not setting status as failed when our test is failing, we are setting only throwable which is AssertionError in failed tests. ** This was working with previous version of testng as in previous version it's checking only exception thrown, not it's status. ** So to work with testng 6.11 we have to set status as failed with throwable. ** https://github.com/cbeust/testng/commit/8fba9498efaaec18ce23572fc5a95afb6d9554c3#diff-b3080bc9d91f177f63b5fd4d9c501364R1326 * Why new SkipExecption() is not able to skip tests in case of remote execution. ** If we have some tests as Skipped then in the result we are not setting it's throwable, we are setting only status as skipped, but after this testng is overriding it's status as success as it doesn't have throwable which is skipException here ** So to fix it set throwable even if test is skipping. ** https://github.com/dipak-pawar/arquillian-core/commit/d93431d38e18b2b54e9c17bd17c88adc0080c151#diff-4417a7a63a141484c8ecb8e3958a3924R64 * Root cause of failure of TestNGIntegrationTestCase is testng ** Look for fix https://github.com/cbeust/testng/pull/1427 All work is done look [here|https://github.com/dipak-pawar/arquillian-core/tree/testng_issue], waiting to merge upstream pr. Thanks, Dipak > Test failures not reported with recent versions of TestNG > --------------------------------------------------------- > > Key: ARQ-2086 > URL: https://issues.jboss.org/browse/ARQ-2086 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.12.Final > Reporter: Gunnar Morling > Assignee: Bartosz Majsak > Priority: Blocker > > When using recent TestNG versions (> 6.8.21) with Arquillian, failing tests are accidentally reported as passing. > A reproducer can be found at https://github.com/gunnarmorling/arquillian-testng-bug. > There is a single test which is expected to fail, but it actually is reported as successful with TestNG 6.11. It is reported as failed as expected with 6.8.21. Run {{mvn clean install}} for reproducing. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 8 06:11:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Mon, 8 May 2017 06:11:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2086) Test failures not reported with recent versions of TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-2086: ----------------------------------- Assignee: Dipak Pawar (was: Bartosz Majsak) > Test failures not reported with recent versions of TestNG > --------------------------------------------------------- > > Key: ARQ-2086 > URL: https://issues.jboss.org/browse/ARQ-2086 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.12.Final > Reporter: Gunnar Morling > Assignee: Dipak Pawar > Priority: Blocker > > When using recent TestNG versions (> 6.8.21) with Arquillian, failing tests are accidentally reported as passing. > A reproducer can be found at https://github.com/gunnarmorling/arquillian-testng-bug. > There is a single test which is expected to fail, but it actually is reported as successful with TestNG 6.11. It is reported as failed as expected with 6.8.21. Run {{mvn clean install}} for reproducing. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 10 04:11:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 10 May 2017 04:11:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2111) Update Selenium to 3.4.0 In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2111: ----------------------------------- Summary: Update Selenium to 3.4.0 Key: ARQ-2111 URL: https://issues.jboss.org/browse/ARQ-2111 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_2.1.0 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.1.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 10 10:00:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 10 May 2017 10:00:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2112) Don't check the latest release of PhantomJS as there won't be any newer In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2112: ----------------------------------- Summary: Don't check the latest release of PhantomJS as there won't be any newer Key: ARQ-2112 URL: https://issues.jboss.org/browse/ARQ-2112 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_2.1.0 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.1.1 Don't check the latest release as there was announced the end of the development of PhantomJS: https://groups.google.com/forum/#!msg/phantomjs/9aI5d-LDuNE/5Z3SMZrqAQAJ It is expected that there won't be any newer version than the last one: 2.1.1 - the checking is an unnecessary operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 02:19:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Thu, 11 May 2017 02:19:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2086) Test failures not reported with recent versions of TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404727#comment-13404727 ] Dipak Pawar edited comment on ARQ-2086 at 5/11/17 2:18 AM: ----------------------------------------------------------- Testng team accepted [issue|https://github.com/cbeust/testng/issues/1426], they merged [fix|https://github.com/cbeust/testng/pull/1432] as well. We are waiting for them to release new version. was (Author: dipakpawar231): Testng team accepted [issue|https://github.com/cbeust/testng/issues/1426], they merged fix as well. We are waiting for them to release new version. > Test failures not reported with recent versions of TestNG > --------------------------------------------------------- > > Key: ARQ-2086 > URL: https://issues.jboss.org/browse/ARQ-2086 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.12.Final > Reporter: Gunnar Morling > Assignee: Dipak Pawar > Priority: Blocker > > When using recent TestNG versions (> 6.8.21) with Arquillian, failing tests are accidentally reported as passing. > A reproducer can be found at https://github.com/gunnarmorling/arquillian-testng-bug. > There is a single test which is expected to fail, but it actually is reported as successful with TestNG 6.11. It is reported as failed as expected with 6.8.21. Run {{mvn clean install}} for reproducing. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 02:19:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Thu, 11 May 2017 02:19:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2086) Test failures not reported with recent versions of TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404727#comment-13404727 ] Dipak Pawar commented on ARQ-2086: ---------------------------------- Testng team accepted [issue|https://github.com/cbeust/testng/issues/1426], they merge fix as well. We are waiting for them to release new version. > Test failures not reported with recent versions of TestNG > --------------------------------------------------------- > > Key: ARQ-2086 > URL: https://issues.jboss.org/browse/ARQ-2086 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.12.Final > Reporter: Gunnar Morling > Assignee: Dipak Pawar > Priority: Blocker > > When using recent TestNG versions (> 6.8.21) with Arquillian, failing tests are accidentally reported as passing. > A reproducer can be found at https://github.com/gunnarmorling/arquillian-testng-bug. > There is a single test which is expected to fail, but it actually is reported as successful with TestNG 6.11. It is reported as failed as expected with 6.8.21. Run {{mvn clean install}} for reproducing. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 02:19:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Thu, 11 May 2017 02:19:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2086) Test failures not reported with recent versions of TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404727#comment-13404727 ] Dipak Pawar edited comment on ARQ-2086 at 5/11/17 2:18 AM: ----------------------------------------------------------- Testng team accepted [issue|https://github.com/cbeust/testng/issues/1426], they merged fix as well. We are waiting for them to release new version. was (Author: dipakpawar231): Testng team accepted [issue|https://github.com/cbeust/testng/issues/1426], they merge fix as well. We are waiting for them to release new version. > Test failures not reported with recent versions of TestNG > --------------------------------------------------------- > > Key: ARQ-2086 > URL: https://issues.jboss.org/browse/ARQ-2086 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.12.Final > Reporter: Gunnar Morling > Assignee: Dipak Pawar > Priority: Blocker > > When using recent TestNG versions (> 6.8.21) with Arquillian, failing tests are accidentally reported as passing. > A reproducer can be found at https://github.com/gunnarmorling/arquillian-testng-bug. > There is a single test which is expected to fail, but it actually is reported as successful with TestNG 6.11. It is reported as failed as expected with 6.8.21. Run {{mvn clean install}} for reproducing. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 07:16:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 11 May 2017 07:16:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2112) Don't check the latest release of PhantomJS as there won't be any newer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2112: -------------------------------- Issue Type: Feature Request (was: Component Upgrade) > Don't check the latest release of PhantomJS as there won't be any newer > ----------------------------------------------------------------------- > > Key: ARQ-2112 > URL: https://issues.jboss.org/browse/ARQ-2112 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.1 > > > Don't check the latest release as there was announced the end of the development of PhantomJS: > https://groups.google.com/forum/#!msg/phantomjs/9aI5d-LDuNE/5Z3SMZrqAQAJ > It is expected that there won't be any newer version than the last one: 2.1.1 - the checking is an unnecessary operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 07:45:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 11 May 2017 07:45:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-503) Update Arquillian Drone to 2.1.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-503: ---------------------------------- Summary: Update Arquillian Drone to 2.1.1 (was: Update Arquillian Drone to 2.1.0) > Update Arquillian Drone to 2.1.1 > -------------------------------- > > Key: ARQGRA-503 > URL: https://issues.jboss.org/browse/ARQGRA-503 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Affects Versions: 2.2.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.2.1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 09:12:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 11 May 2017 09:12:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2112) Don't check the latest release of PhantomJS as there won't be any newer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2112: -------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/88 > Don't check the latest release of PhantomJS as there won't be any newer > ----------------------------------------------------------------------- > > Key: ARQ-2112 > URL: https://issues.jboss.org/browse/ARQ-2112 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.1 > > > Don't check the latest release as there was announced the end of the development of PhantomJS: > https://groups.google.com/forum/#!msg/phantomjs/9aI5d-LDuNE/5Z3SMZrqAQAJ > It is expected that there won't be any newer version than the last one: 2.1.1 - the checking is an unnecessary operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 09:12:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 11 May 2017 09:12:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2112) Don't check the latest release of PhantomJS as there won't be any newer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2112. ------------------------------- Resolution: Done pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/babb8c41440170971ebd696a7dae3a3a3e88ebcc > Don't check the latest release of PhantomJS as there won't be any newer > ----------------------------------------------------------------------- > > Key: ARQ-2112 > URL: https://issues.jboss.org/browse/ARQ-2112 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.1 > > > Don't check the latest release as there was announced the end of the development of PhantomJS: > https://groups.google.com/forum/#!msg/phantomjs/9aI5d-LDuNE/5Z3SMZrqAQAJ > It is expected that there won't be any newer version than the last one: 2.1.1 - the checking is an unnecessary operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 09:13:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 11 May 2017 09:13:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2111) Update Selenium to 3.4.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2111. ------------------------------- Resolution: Done Done by https://github.com/arquillian/arquillian-extension-drone/commit/d5c71ee7ccb7b7d902e99442ecc874e3c75b8b98 > Update Selenium to 3.4.0 > ------------------------ > > Key: ARQ-2111 > URL: https://issues.jboss.org/browse/ARQ-2111 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.1.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 09:16:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 11 May 2017 09:16:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-503) Update Arquillian Drone to 2.1.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-503. --------------------------------- Resolution: Done Done by https://github.com/arquillian/arquillian-graphene/commit/0e2a9faaa6913f235234aa5b5125419a813b4054 > Update Arquillian Drone to 2.1.1 > -------------------------------- > > Key: ARQGRA-503 > URL: https://issues.jboss.org/browse/ARQGRA-503 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Affects Versions: 2.2.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.2.1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 09:16:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 11 May 2017 09:16:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-502) Update Arquillian-core to 1.1.13.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-502. --------------------------------- Resolution: Done Done by https://github.com/arquillian/arquillian-graphene/commit/22eff5371a5acf90ceee694fe6cc299c62020e44 > Update Arquillian-core to 1.1.13.Final > -------------------------------------- > > Key: ARQGRA-502 > URL: https://issues.jboss.org/browse/ARQGRA-502 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Affects Versions: 2.2.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.2.1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 09:21:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 11 May 2017 09:21:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-484) Enriched element is not equal to the same element In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-484. --------------------------------- Assignee: Vsevolod Golovanov Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-graphene/commit/3ef8438cde52b0ba0617f8cd6db733de2e82aa1e > Enriched element is not equal to the same element > ------------------------------------------------- > > Key: ARQGRA-484 > URL: https://issues.jboss.org/browse/ARQGRA-484 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha3 > Reporter: Ji?? ?tefek > Assignee: Vsevolod Golovanov > > After upgrading to 2.1.0.Alpha3 from Alpha2, the following (simplified) test won't pass: > {code} > @FindBy(id="id") > private WebElement e; > @Test > private void test(){ > e.equals(e) > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 09:23:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 11 May 2017 09:23:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-484) Enriched element is not equal to the same element In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reopened ARQGRA-484: ----------------------------------- > Enriched element is not equal to the same element > ------------------------------------------------- > > Key: ARQGRA-484 > URL: https://issues.jboss.org/browse/ARQGRA-484 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha3 > Reporter: Ji?? ?tefek > Assignee: Vsevolod Golovanov > Fix For: 2.2.1 > > > After upgrading to 2.1.0.Alpha3 from Alpha2, the following (simplified) test won't pass: > {code} > @FindBy(id="id") > private WebElement e; > @Test > private void test(){ > e.equals(e) > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 09:23:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 11 May 2017 09:23:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-484) Enriched element is not equal to the same element In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-484: ---------------------------------- Fix Version/s: 2.2.1 > Enriched element is not equal to the same element > ------------------------------------------------- > > Key: ARQGRA-484 > URL: https://issues.jboss.org/browse/ARQGRA-484 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha3 > Reporter: Ji?? ?tefek > Assignee: Vsevolod Golovanov > Fix For: 2.2.1 > > > After upgrading to 2.1.0.Alpha3 from Alpha2, the following (simplified) test won't pass: > {code} > @FindBy(id="id") > private WebElement e; > @Test > private void test(){ > e.equals(e) > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 11 09:23:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 11 May 2017 09:23:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-484) Enriched element is not equal to the same element In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-484. --------------------------------- Resolution: Done > Enriched element is not equal to the same element > ------------------------------------------------- > > Key: ARQGRA-484 > URL: https://issues.jboss.org/browse/ARQGRA-484 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha3 > Reporter: Ji?? ?tefek > Assignee: Vsevolod Golovanov > Fix For: 2.2.1 > > > After upgrading to 2.1.0.Alpha3 from Alpha2, the following (simplified) test won't pass: > {code} > @FindBy(id="id") > private WebElement e; > @Test > private void test(){ > e.equals(e) > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 12 03:12:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Fri, 12 May 2017 03:12:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2113) Support for Infinispan seeding in standalone DSL In-Reply-To: References: Message-ID: Alex Soto created ARQ-2113: ------------------------------ Summary: Support for Infinispan seeding in standalone DSL Key: ARQ-2113 URL: https://issues.jboss.org/browse/ARQ-2113 Project: Arquillian Issue Type: Sub-task Components: Extension - Persistence Reporter: Alex Soto Assignee: Bartosz Majsak -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 12 03:13:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Fri, 12 May 2017 03:13:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2113) Support for Infinispan seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto reassigned ARQ-2113: ------------------------------ Assignee: Alex Soto (was: Bartosz Majsak) > Support for Infinispan seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2113 > URL: https://issues.jboss.org/browse/ARQ-2113 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 12 03:13:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Fri, 12 May 2017 03:13:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2113) Support for Infinispan seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-2113: --------------------------- Fix Version/s: persistence_1.0.0.next > Support for Infinispan seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2113 > URL: https://issues.jboss.org/browse/ARQ-2113 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 12 04:17:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Fri, 12 May 2017 04:17:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2113) Support for Infinispan seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-2113 started by Alex Soto. -------------------------------------- > Support for Infinispan seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2113 > URL: https://issues.jboss.org/browse/ARQ-2113 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 12 04:20:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Fri, 12 May 2017 04:20:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2088) When test is skipped because of an assumption, Arquillian's test result is passed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dipak Pawar reassigned ARQ-2088: -------------------------------- Assignee: Dipak Pawar > When test is skipped because of an assumption, Arquillian's test result is passed > --------------------------------------------------------------------------------- > > Key: ARQ-2088 > URL: https://issues.jboss.org/browse/ARQ-2088 > Project: Arquillian > Issue Type: Enhancement > Components: core > Affects Versions: 1.1.13.Final > Reporter: Matous Jobanek > Assignee: Dipak Pawar > > When you run Arquillian test with an assumption: {{Assume.assumeFalse(true);}} then the test is skipped. The same also say both IDE and maven surefire, but Arquillian's {{TestResult}} retrieved in {{After}} phase contains status Passed. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 12 04:20:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Fri, 12 May 2017 04:20:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2088) When test is skipped because of an assumption, Arquillian's test result is passed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405481#comment-13405481 ] Dipak Pawar commented on ARQ-2088: ---------------------------------- It has nothing to do with core, we have bug in reporter. Look for following events {code} (E) ManagerProcessing (O) LoadableExtensionLoader.load (E) ServiceRegistryLoader (E) ManagerStarted (O) ReporterLifecycleManager.observeFirstEvent (E) ExecutionStore (O) ConfigurationRegistrar.loadConfiguration (E) ArquillianDescriptorImpl (O) ProtocolRegistryCreator.createRegistry (E) ProtocolRegistry (O) ContainerRegistryCreator.createRegistry (E) LocalContainerRegistry (O) ReporterConfigurator.configure (E) ReporterConfiguration (E) BeforeSuite (I) TestContextHandler.createSuiteContext (O) ArquillianCoreReporterLifecycleManager.startTestSuite (E) TestSuiteSection (O) ReporterLifecycleManager.observeEventsForAllSections (O) ContainerEventController.execute (E) SetupContainers (O) ClientDeployerCreator.createClientSideDeployer (E) ClientDeployer (O) ClientContainerControllerCreator.createClientSideContainerController (E) ClientContainerController (O) ContainerLifecycleController.setupContainers (E) StartSuiteContainers (O) ContainerLifecycleController.startSuiteContainers (O) EnvironmentReportCreator.startTestSuite (E) TestSuiteConfigurationSection (O) ReporterLifecycleManager.observeEventsForAllSections (E) BeforeClass (I) TestContextHandler.createSuiteContext (I) TestContextHandler.createClassContext (E) TestClass (O) ArquillianCoreReporterLifecycleManager.startTestClass (E) TestClassSection (O) ReporterLifecycleManager.observeEventsForAllSections (O) ContainerEventController.execute (E) StartClassContainers (O) ContainerLifecycleController.startClassContainers (E) GenerateDeployment (O) DeploymentGenerator.generateDeployment (E) DeploymentScenario (E) DeployManagedDeployments (O) ContainerDeployController.deployManaged (O) ContainerRestarter.restart (O) ClientBeforeAfterLifecycleEventExecuter.on (E) RulesEnrichment (I) TestContextHandler.createSuiteContext (I) TestContextHandler.createClassContext (E) TestClass (I) TestContextHandler.createTestContext (I) ContainerEventController.createBeforeContext (O) RulesEnricher.enrichRulesAndTestInstance (O) ClientBeforeAfterLifecycleEventExecuter.on (E) BeforeRules (I) TestContextHandler.createSuiteContext (I) TestContextHandler.createClassContext (E) TestClass (I) TestContextHandler.createTestContext (I) ContainerEventController.createBeforeContext (O) RulesEnricher.enrichStatement (E) BeforeEnrichment (E) AfterEnrichment (O) ClientBeforeAfterLifecycleEventExecuter.on (E) Before (I) TestContextHandler.createSuiteContext (I) TestContextHandler.createClassContext (E) TestClass (I) TestContextHandler.createTestContext (I) ContainerEventController.createBeforeContext (O) ArquillianCoreReporterLifecycleManager.startTestMethod (E) TestMethodSection (O) ReporterLifecycleManager.observeEventsForAllSections (O) TestInstanceEnricher.enrich (E) BeforeEnrichment (E) AfterEnrichment (O) ClientBeforeAfterLifecycleEventExecuter.on (E) Test (I) TestContextHandler.createSuiteContext (I) TestContextHandler.createClassContext (E) TestClass (I) TestContextHandler.createTestContext (I) ContainerEventController.createTestContext (O) ClientTestExecuter.execute (E) LocalExecutionEvent (O) LocalTestExecuter.execute This should fail (E) TestResult (E) After (I) TestContextHandler.createSuiteContext (I) TestContextHandler.createClassContext (E) TestClass (I) TestContextHandler.createTestContext (I) UpdateTestResultBeforeAfter.update (I) ContainerEventController.createAfterContext (O) ClientBeforeAfterLifecycleEventExecuter.on (O) ArquillianCoreReporterLifecycleManager.stopTestMethod (E) TestMethodSection (O) ReporterLifecycleManager.observeEventsForAllSections (E) ComparisonFailure (E) ComparisonFailure (E) AfterRules (I) TestContextHandler.createSuiteContext (I) TestContextHandler.createClassContext (E) TestClass (I) TestContextHandler.createTestContext (I) UpdateTestResultBeforeAfter.update (I) ContainerEventController.createAfterContext (O) ClientBeforeAfterLifecycleEventExecuter.on (O) ArquillianCoreReporterLifecycleManager.stopTestMethod (E) TestMethodSection (O) ReporterLifecycleManager.observeEventsForAllSections (E) AfterClass (I) TestContextHandler.createSuiteContext (I) TestContextHandler.createClassContext (E) TestClass (O) ClientBeforeAfterLifecycleEventExecuter.on (O) ContainerEventController.execute (E) UnDeployManagedDeployments (O) ContainerDeployController.undeployManaged (E) StopManualContainers (O) ContainerLifecycleController.stopManualContainers (E) StopClassContainers (O) ContainerLifecycleController.stopClassContainers (O) ArquillianCoreReporterLifecycleManager.stopTestClass (E) TestClassSection (O) ReporterLifecycleManager.observeEventsForAllSections Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.669 sec <<< FAILURE! - in org.arquillian.reporter.FailingTest runFailingTest(org.arquillian.reporter.FailingTest) Time elapsed: 0.095 sec <<< FAILURE! org.junit.ComparisonFailure: expected:<[0]> but was:<[1]> at org.arquillian.reporter.FailingTest.runFailingTest(FailingTest.java:25) (E) AfterSuite (I) TestContextHandler.createSuiteContext (O) ContainerEventController.execute (E) StopSuiteContainers (O) ContainerLifecycleController.stopSuiteContainers (O) ArquillianCoreReporterLifecycleManager.stopTestSuite (E) TestSuiteSection (O) ReporterLifecycleManager.observeEventsForAllSections (E) ManagerStopping (O) ReporterLifecycleManager.observeLastEvent {code} We are observing wrong event `AfterTest` in reporter. We should observe `AfterTestLifecycleEvent` from which AfterTest is inhereting, invoke fire for reporter only if observing event is instance of `AfterTestLifeCycleEvent` Opened isssue for reporter on [GH|https://github.com/arquillian/arquillian-reporter/issues/20]. Fixed in [PR|https://github.com/arquillian/arquillian-reporter/pull/21] Thanks, Dipak > When test is skipped because of an assumption, Arquillian's test result is passed > --------------------------------------------------------------------------------- > > Key: ARQ-2088 > URL: https://issues.jboss.org/browse/ARQ-2088 > Project: Arquillian > Issue Type: Enhancement > Components: core > Affects Versions: 1.1.13.Final > Reporter: Matous Jobanek > > When you run Arquillian test with an assumption: {{Assume.assumeFalse(true);}} then the test is skipped. The same also say both IDE and maven surefire, but Arquillian's {{TestResult}} retrieved in {{After}} phase contains status Passed. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat May 13 03:47:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Sat, 13 May 2017 03:47:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2113) Support for Infinispan seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-2113: --------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/81 > Support for Infinispan seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2113 > URL: https://issues.jboss.org/browse/ARQ-2113 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 15 03:56:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Mon, 15 May 2017 03:56:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2113) Support for Infinispan seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-2113 started by Alex Soto. -------------------------------------- > Support for Infinispan seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2113 > URL: https://issues.jboss.org/browse/ARQ-2113 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 15 03:56:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Mon, 15 May 2017 03:56:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2113) Support for Infinispan seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-2113 stopped by Alex Soto. -------------------------------------- > Support for Infinispan seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2113 > URL: https://issues.jboss.org/browse/ARQ-2113 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 15 03:56:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Mon, 15 May 2017 03:56:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2113) Support for Infinispan seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-2113: --------------------------- Status: Pull Request Sent (was: Coding In Progress) > Support for Infinispan seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2113 > URL: https://issues.jboss.org/browse/ARQ-2113 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 15 05:27:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Mon, 15 May 2017 05:27:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2113) Support for Infinispan seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto closed ARQ-2113. -------------------------- Resolution: Done Upstream: https://github.com/arquillian/arquillian-extension-persistence/commit/1c9f9c86b35735457b565c9ddc24c63dd60fcaa9 > Support for Infinispan seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2113 > URL: https://issues.jboss.org/browse/ARQ-2113 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 15 07:29:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Mon, 15 May 2017 07:29:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2047) Use of Java 8 lambdas by injected class causes injection to fail silently In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406214#comment-13406214 ] Dipak Pawar commented on ARQ-2047: ---------------------------------- [~cthorburn8], I have tried to reproduce this issue as per steps mentioned by you. But I couldn't reproduce your mentioned behavior for lambda expression. You can look for my test project [here|https://github.com/dipak-pawar/ARQ-2047-test] Can you please try to share your project where this issue is reproducing? Maybe something is missing in my project. > Use of Java 8 lambdas by injected class causes injection to fail silently > ------------------------------------------------------------------------- > > Key: ARQ-2047 > URL: https://issues.jboss.org/browse/ARQ-2047 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: Eclipse Neon, Windows > Reporter: Colin Thorburn > > Have seen this bug elsewhere marked as resolved but it clearly isn't. > To reproduce simply create a Junit 4 Arquiliian test in which EntityManager and UserTransaction fields are annontated for injection. > Devise an @Test method contriving the use of (say) Runnable. Call a method in another class using the Runnable as a parameter > Code using an anonymous inner class idiom; everything works fine. > Code it as a lambda expression and, bizarrely, only the EntityManager is not injected (utx is OK!). No hint of anything awry in the log, no exception thrown, field is simply left null. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 15 07:43:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Mon, 15 May 2017 07:43:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2047) Use of Java 8 lambdas by injected class causes injection to fail silently In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406214#comment-13406214 ] Dipak Pawar edited comment on ARQ-2047 at 5/15/17 7:42 AM: ----------------------------------------------------------- [~cthorburn8], I have tried to reproduce this issue as per steps mentioned by you. But I couldn't reproduce your mentioned behavior for lambda expression. You can look for my test project [here|https://github.com/dipak-pawar/ARQ-2047-test] Can you please share your project where this issue is reproducing? Maybe something is missing in my project. was (Author: dipakpawar231): [~cthorburn8], I have tried to reproduce this issue as per steps mentioned by you. But I couldn't reproduce your mentioned behavior for lambda expression. You can look for my test project [here|https://github.com/dipak-pawar/ARQ-2047-test] Can you please try to share your project where this issue is reproducing? Maybe something is missing in my project. > Use of Java 8 lambdas by injected class causes injection to fail silently > ------------------------------------------------------------------------- > > Key: ARQ-2047 > URL: https://issues.jboss.org/browse/ARQ-2047 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: Eclipse Neon, Windows > Reporter: Colin Thorburn > > Have seen this bug elsewhere marked as resolved but it clearly isn't. > To reproduce simply create a Junit 4 Arquiliian test in which EntityManager and UserTransaction fields are annontated for injection. > Devise an @Test method contriving the use of (say) Runnable. Call a method in another class using the Runnable as a parameter > Code using an anonymous inner class idiom; everything works fine. > Code it as a lambda expression and, bizarrely, only the EntityManager is not injected (utx is OK!). No hint of anything awry in the log, no exception thrown, field is simply left null. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 16 01:39:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Tue, 16 May 2017 01:39:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2047) Use of Java 8 lambdas by injected class causes injection to fail silently In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dipak Pawar reassigned ARQ-2047: -------------------------------- Assignee: Dipak Pawar > Use of Java 8 lambdas by injected class causes injection to fail silently > ------------------------------------------------------------------------- > > Key: ARQ-2047 > URL: https://issues.jboss.org/browse/ARQ-2047 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: Eclipse Neon, Windows > Reporter: Colin Thorburn > Assignee: Dipak Pawar > > Have seen this bug elsewhere marked as resolved but it clearly isn't. > To reproduce simply create a Junit 4 Arquiliian test in which EntityManager and UserTransaction fields are annontated for injection. > Devise an @Test method contriving the use of (say) Runnable. Call a method in another class using the Runnable as a parameter > Code using an anonymous inner class idiom; everything works fine. > Code it as a lambda expression and, bizarrely, only the EntityManager is not injected (utx is OK!). No hint of anything awry in the log, no exception thrown, field is simply left null. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 18 11:09:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 18 May 2017 11:09:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2114) It is easy to reach the GH rate limit when firefox is used In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2114: ----------------------------------- Summary: It is easy to reach the GH rate limit when firefox is used Key: ARQ-2114 URL: https://issues.jboss.org/browse/ARQ-2114 Project: Arquillian Issue Type: Bug Components: Extension - Drone Affects Versions: drone_2.1.1 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.1.2 When the limit is reached, then you get this error: {noformat} 07:48:53 java.lang.RuntimeException: Could not create statement 07:48:53 at org.jboss.arquillian.junit.Arquillian.methodBlock(Arquillian.java:360) 07:48:53 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) 07:48:53 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) 07:48:53 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) 07:48:53 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) 07:48:53 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) 07:48:53 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) 07:48:53 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) 07:48:53 at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:205) 07:48:53 at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431) 07:48:53 at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55) 07:48:53 at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:219) 07:48:53 at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) 07:48:53 at org.junit.rules.RunRules.evaluate(RunRules.java:20) 07:48:53 at org.junit.runners.ParentRunner.run(ParentRunner.java:363) 07:48:53 at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:167) 07:48:53 at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) 07:48:53 at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) 07:48:53 at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) 07:48:53 at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) 07:48:53 at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) 07:48:53 at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) 07:48:53 at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) 07:48:53 Caused by: java.lang.IllegalStateException: Something bad happened when Drone was trying to download and prepare a binary. For more information see the cause. 07:48:53 at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.checkAndSetBinary(AbstractBinaryHandler.java:61) 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.getCapabilities(FirefoxDriverFactory.java:107) 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:73) 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:39) 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:127) 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:38) 07:48:53 at org.jboss.arquillian.drone.impl.DroneConfigurator$1.createInstance(DroneConfigurator.java:112) 07:48:53 at org.jboss.arquillian.drone.impl.CachingCallableImpl.call(CachingCallableImpl.java:44) 07:48:53 at org.jboss.arquillian.core.impl.threading.ThreadedExecutorService$ContextualCallable.call(ThreadedExecutorService.java:89) 07:48:53 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 07:48:53 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 07:48:53 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 07:48:53 at java.lang.Thread.run(Thread.java:745) 07:48:53 Caused by: java.lang.IllegalStateException: This is not a JSON Array. 07:48:53 at com.google.gson.JsonElement.getAsJsonArray(JsonElement.java:106) 07:48:53 at org.jboss.arquillian.drone.webdriver.binary.downloading.source.GitHubSource.getReleaseForVersion(GitHubSource.java:103) 07:48:53 at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.downloadAndPrepare(AbstractBinaryHandler.java:161) 07:48:53 at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.checkAndSetBinary(AbstractBinaryHandler.java:59) 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.getCapabilities(FirefoxDriverFactory.java:107) 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:73) 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:39) 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:127) 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:38) 07:48:53 at org.jboss.arquillian.drone.impl.DroneConfigurator$1.createInstance(DroneConfigurator.java:112) 07:48:53 at org.jboss.arquillian.drone.impl.CachingCallableImpl.call(CachingCallableImpl.java:44) 07:48:53 at org.jboss.arquillian.core.impl.threading.ThreadedExecutorService$ContextualCallable.call(ThreadedExecutorService.java:89) 07:48:53 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 07:48:53 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 07:48:53 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 07:48:53 at java.lang.Thread.run(Thread.java:745) {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 18 11:51:00 2017 From: issues at jboss.org (=?UTF-8?Q?Cristina_Gonz=C3=A1lez_castellano_=28JIRA=29?=) Date: Thu, 18 May 2017 11:51:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2016) Improve the ability to add custom extensions for the containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408395#comment-13408395 ] Cristina Gonz?lez castellano commented on ARQ-2016: --------------------------------------------------- Hello!, We have adapt the Arquillian OSGi Extension so it can use custom extensions, now we are using it sucessfully in the Arquillian Liferay Extension. The idea that we have implemented is: 1. The Arquillian OSGi Bundle is automatically generated (with all the extensions that are declared in the classpath). (This is done only once) 2. For every test: 2.1. The Arquillian OSGi Bundle is installed. 2.2. The test deployment is installed without any enhacement. 2.3. A fragment for the Arquillian OSGI Bundle that contains only the test class is generated and installed. 2.4 The tests are executed 2.5 All the previously installed bundle are uninstalled. We have created a pull (https://github.com/arquillian/arquillian-container-osgi/pull/51) were you can check the changes. We think that this maybe can be usefull for someone. Maybe it would be interesting try to merge it with the current Arquillian OSGi Container. What do you think? If you need more information, please, let us know. Thanks! > Improve the ability to add custom extensions for the containers > --------------------------------------------------------------- > > Key: ARQ-2016 > URL: https://issues.jboss.org/browse/ARQ-2016 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Affects Versions: osgi_2.1.0.Final > Environment: Under Linux, and inside Karaf 4.x > Reporter: Steve Storck > > When the arquillian-container-osgi extension is deployed, it also deploys the arquillian-osgi-bundle. This bundle exposes a few APIs, but it contains (and does not expose) some of the implementation and SPI packages. This effectively results in only being able to use the provided JUnitBundleTestRunner extension. I want to use the arquillian-testrunner-spock extension, but it always fails because I have to deploy the test SPI bundle with my test jar, and it conflicts with those packages that the arquillian-osgi-bundle uses internally. This causes an exception to be thrown that complains that the EventTestRunnerAdaptor implementation is not an instance of the TestRunnerAdaptor interface. The chain of events that results in the exception is as follows: > {code:java|title=ArquillianSputnik.java (arquillian-testrunner-spock)|borderStyle=solid} > package org.jboss.arquillian.spock; > public class ArquillianSputnik extends Sputnik { > import org.jboss.arquillian.test.spi.TestRunnerAdaptor; > import org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder; > // Methods and fields omitted for brevity, but you can see that the > // proper packages are imported > public void run(RunNotifier notifier) { > // Code omitted for brevity > final TestRunnerAdaptor adaptor = TestRunnerAdaptorBuilder.build(); > // More code omitted for brevity > } > } > {code} > {code:java|title=EventTestRunnerAdaptorBuilder.java (arquillian-core test/spi)|borderStyle=solid} > package org.jboss.arquillian.test.spi; > public class TestRunnerAdaptorBuilder { > private static final String DEFAULT_EXTENSION_CLASS = > "org.jboss.arquillian.core.impl.loadable.LoadableExtensionLoader"; > private static final String TEST_RUNNER_IMPL_CLASS = > "org.jboss.arquillian.test.impl.EventTestRunnerAdaptor"; > public static TestRunnerAdaptor build() { > // omitted lines for brevity > ManagerBuilder builder = ManagerBuilder.from() > .extension(SecurityActions.loadClass(DEFAULT_EXTENSION_CLASS)); > return SecurityActions.newInstance( > TEST_RUNNER_IMPL_CLASS, > new Class[] {ManagerBuilder.class}, > new Object[] {builder}, > TestRunnerAdaptor.class); > } > } > {code} > {code:java|title=SecurityActions.java (arquillian-core test/spi)|borderStyle=solid} > package org.jboss.arquillian.test.spi; > final class SecurityActions { > static T newInstance(final String className, > final Class[] argumentTypes, > final Object[] arguments, > final Class expectedType) { > @SuppressWarnings("unchecked") > Class implClass = (Class) loadClass(className); > if (!expectedType.isAssignableFrom(implClass)) { > throw new RuntimeException("Loaded class " + > className + > " is not of expected type " + > expectedType); > } > return newInstance(implClass, argumentTypes, arguments); > } > } > {code} > I think that the best solution would be to completely decouple the JUnitTestRunner from the container modules, or at the very least, it would be good to change the <_exportcontents> to export most (or all) of the embedded dependency packages so that users can make use of other extensions, or build their own. > Edit: After some more thought, it would be really nice to make test extensions loadable (with a default if it is unspecified, of course). I don't know enough about the code base (yet) to say if it would be best to do this via an annotation, or if pluggability would be better leveraged somewhere else in the framework. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 22 03:15:00 2017 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Mon, 22 May 2017 03:15:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2016) Improve the ability to add custom extensions for the containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler reassigned ARQ-2016: ----------------------------------- Assignee: Thomas Diesler > Improve the ability to add custom extensions for the containers > --------------------------------------------------------------- > > Key: ARQ-2016 > URL: https://issues.jboss.org/browse/ARQ-2016 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Affects Versions: osgi_2.1.0.Final > Environment: Under Linux, and inside Karaf 4.x > Reporter: Steve Storck > Assignee: Thomas Diesler > > When the arquillian-container-osgi extension is deployed, it also deploys the arquillian-osgi-bundle. This bundle exposes a few APIs, but it contains (and does not expose) some of the implementation and SPI packages. This effectively results in only being able to use the provided JUnitBundleTestRunner extension. I want to use the arquillian-testrunner-spock extension, but it always fails because I have to deploy the test SPI bundle with my test jar, and it conflicts with those packages that the arquillian-osgi-bundle uses internally. This causes an exception to be thrown that complains that the EventTestRunnerAdaptor implementation is not an instance of the TestRunnerAdaptor interface. The chain of events that results in the exception is as follows: > {code:java|title=ArquillianSputnik.java (arquillian-testrunner-spock)|borderStyle=solid} > package org.jboss.arquillian.spock; > public class ArquillianSputnik extends Sputnik { > import org.jboss.arquillian.test.spi.TestRunnerAdaptor; > import org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder; > // Methods and fields omitted for brevity, but you can see that the > // proper packages are imported > public void run(RunNotifier notifier) { > // Code omitted for brevity > final TestRunnerAdaptor adaptor = TestRunnerAdaptorBuilder.build(); > // More code omitted for brevity > } > } > {code} > {code:java|title=EventTestRunnerAdaptorBuilder.java (arquillian-core test/spi)|borderStyle=solid} > package org.jboss.arquillian.test.spi; > public class TestRunnerAdaptorBuilder { > private static final String DEFAULT_EXTENSION_CLASS = > "org.jboss.arquillian.core.impl.loadable.LoadableExtensionLoader"; > private static final String TEST_RUNNER_IMPL_CLASS = > "org.jboss.arquillian.test.impl.EventTestRunnerAdaptor"; > public static TestRunnerAdaptor build() { > // omitted lines for brevity > ManagerBuilder builder = ManagerBuilder.from() > .extension(SecurityActions.loadClass(DEFAULT_EXTENSION_CLASS)); > return SecurityActions.newInstance( > TEST_RUNNER_IMPL_CLASS, > new Class[] {ManagerBuilder.class}, > new Object[] {builder}, > TestRunnerAdaptor.class); > } > } > {code} > {code:java|title=SecurityActions.java (arquillian-core test/spi)|borderStyle=solid} > package org.jboss.arquillian.test.spi; > final class SecurityActions { > static T newInstance(final String className, > final Class[] argumentTypes, > final Object[] arguments, > final Class expectedType) { > @SuppressWarnings("unchecked") > Class implClass = (Class) loadClass(className); > if (!expectedType.isAssignableFrom(implClass)) { > throw new RuntimeException("Loaded class " + > className + > " is not of expected type " + > expectedType); > } > return newInstance(implClass, argumentTypes, arguments); > } > } > {code} > I think that the best solution would be to completely decouple the JUnitTestRunner from the container modules, or at the very least, it would be good to change the <_exportcontents> to export most (or all) of the embedded dependency packages so that users can make use of other extensions, or build their own. > Edit: After some more thought, it would be really nice to make test extensions loadable (with a default if it is unspecified, of course). I don't know enough about the code base (yet) to say if it would be best to do this via an annotation, or if pluggability would be better leveraged somewhere else in the framework. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 22 03:24:00 2017 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Mon, 22 May 2017 03:24:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2016) Improve the ability to add custom extensions for the containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-2016. --------------------------------- Resolution: Done Done > Improve the ability to add custom extensions for the containers > --------------------------------------------------------------- > > Key: ARQ-2016 > URL: https://issues.jboss.org/browse/ARQ-2016 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Affects Versions: osgi_2.1.0.Final > Environment: Under Linux, and inside Karaf 4.x > Reporter: Steve Storck > Assignee: Thomas Diesler > > When the arquillian-container-osgi extension is deployed, it also deploys the arquillian-osgi-bundle. This bundle exposes a few APIs, but it contains (and does not expose) some of the implementation and SPI packages. This effectively results in only being able to use the provided JUnitBundleTestRunner extension. I want to use the arquillian-testrunner-spock extension, but it always fails because I have to deploy the test SPI bundle with my test jar, and it conflicts with those packages that the arquillian-osgi-bundle uses internally. This causes an exception to be thrown that complains that the EventTestRunnerAdaptor implementation is not an instance of the TestRunnerAdaptor interface. The chain of events that results in the exception is as follows: > {code:java|title=ArquillianSputnik.java (arquillian-testrunner-spock)|borderStyle=solid} > package org.jboss.arquillian.spock; > public class ArquillianSputnik extends Sputnik { > import org.jboss.arquillian.test.spi.TestRunnerAdaptor; > import org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder; > // Methods and fields omitted for brevity, but you can see that the > // proper packages are imported > public void run(RunNotifier notifier) { > // Code omitted for brevity > final TestRunnerAdaptor adaptor = TestRunnerAdaptorBuilder.build(); > // More code omitted for brevity > } > } > {code} > {code:java|title=EventTestRunnerAdaptorBuilder.java (arquillian-core test/spi)|borderStyle=solid} > package org.jboss.arquillian.test.spi; > public class TestRunnerAdaptorBuilder { > private static final String DEFAULT_EXTENSION_CLASS = > "org.jboss.arquillian.core.impl.loadable.LoadableExtensionLoader"; > private static final String TEST_RUNNER_IMPL_CLASS = > "org.jboss.arquillian.test.impl.EventTestRunnerAdaptor"; > public static TestRunnerAdaptor build() { > // omitted lines for brevity > ManagerBuilder builder = ManagerBuilder.from() > .extension(SecurityActions.loadClass(DEFAULT_EXTENSION_CLASS)); > return SecurityActions.newInstance( > TEST_RUNNER_IMPL_CLASS, > new Class[] {ManagerBuilder.class}, > new Object[] {builder}, > TestRunnerAdaptor.class); > } > } > {code} > {code:java|title=SecurityActions.java (arquillian-core test/spi)|borderStyle=solid} > package org.jboss.arquillian.test.spi; > final class SecurityActions { > static T newInstance(final String className, > final Class[] argumentTypes, > final Object[] arguments, > final Class expectedType) { > @SuppressWarnings("unchecked") > Class implClass = (Class) loadClass(className); > if (!expectedType.isAssignableFrom(implClass)) { > throw new RuntimeException("Loaded class " + > className + > " is not of expected type " + > expectedType); > } > return newInstance(implClass, argumentTypes, arguments); > } > } > {code} > I think that the best solution would be to completely decouple the JUnitTestRunner from the container modules, or at the very least, it would be good to change the <_exportcontents> to export most (or all) of the embedded dependency packages so that users can make use of other extensions, or build their own. > Edit: After some more thought, it would be really nice to make test extensions loadable (with a default if it is unspecified, of course). I don't know enough about the code base (yet) to say if it would be best to do this via an annotation, or if pluggability would be better leveraged somewhere else in the framework. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 22 11:50:00 2017 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Macik_=28JIRA=29?=) Date: Mon, 22 May 2017 11:50:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9 In-Reply-To: References: Message-ID: Mari?n Macik created ARQ-2115: --------------------------------- Summary: Create Arquillian adapter for WebSphere 9 Key: ARQ-2115 URL: https://issues.jboss.org/browse/ARQ-2115 Project: Arquillian Issue Type: Feature Request Components: WebSphere Containers Reporter: Mari?n Macik Assignee: Gerhard Poul Hi, guys, I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR: \#### Short description of what this resolves: Hi, guys, my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: {code} -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar {code} I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. I have also run the enclosed tests with my own arquillian.xml and they have passed. Thanks, Marian -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 22 11:51:00 2017 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Macik_=28JIRA=29?=) Date: Mon, 22 May 2017 11:51:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Macik updated ARQ-2115: ------------------------------ Description: Hi, guys, I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: \#### Short description of what this resolves: Hi, guys, my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: {code} -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar {code} I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. I have also run the enclosed tests with my own arquillian.xml and they have passed. Thanks, Marian [1] was: Hi, guys, I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR: \#### Short description of what this resolves: Hi, guys, my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: {code} -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar {code} I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. I have also run the enclosed tests with my own arquillian.xml and they have passed. Thanks, Marian > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Mari?n Macik > Assignee: Gerhard Poul > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 22 11:52:00 2017 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Macik_=28JIRA=29?=) Date: Mon, 22 May 2017 11:52:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Macik updated ARQ-2115: ------------------------------ Description: Hi, guys, I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: \#### Short description of what this resolves: Hi, guys, my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: {code} -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar {code} I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. I have also run the enclosed tests with my own arquillian.xml and they have passed. Thanks, Marian [1] https://github.com/arquillian/arquillian-container-was/pull/29 was: Hi, guys, I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: \#### Short description of what this resolves: Hi, guys, my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: {code} -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar {code} I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. I have also run the enclosed tests with my own arquillian.xml and they have passed. Thanks, Marian [1] > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Mari?n Macik > Assignee: Gerhard Poul > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] https://github.com/arquillian/arquillian-container-was/pull/29 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 22 11:52:00 2017 From: issues at jboss.org (=?UTF-8?Q?Mari=C3=A1n_Macik_=28JIRA=29?=) Date: Mon, 22 May 2017 11:52:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mari?n Macik updated ARQ-2115: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-was/pull/29 > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Mari?n Macik > Assignee: Gerhard Poul > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] https://github.com/arquillian/arquillian-container-was/pull/29 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 04:51:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 May 2017 04:51:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1892) java.util.NoSuchElementException from TestRunner class getTestRunner method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410347#comment-13410347 ] Bartosz Majsak commented on ARQ-1892: ------------------------------------- Is it still an issue with latest Arquilian [~saurabh_ksa]? > java.util.NoSuchElementException from TestRunner class getTestRunner method > --------------------------------------------------------------------------- > > Key: ARQ-1892 > URL: https://issues.jboss.org/browse/ARQ-1892 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.5.Final > Environment: RSA, WAS 8.x > Reporter: Saurabh Agarwal > Priority: Critical > Attachments: ArquillianSampleTest.java, SampleBean.java, SampleBeanNonCDI.java, arquillian.xml > > > Hi All, > Upon running test case with Arqullian, I am getting below exception from TestRunner.class in getTest method. > I am using Servlet 3.0 protocol. > java.util.NoSuchElementException > at java.util.LinkedHashMap$AbstractMapIterator.makeNext(LinkedHashMap.java:143) > at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:201) > at org.jboss.arquillian.container.test.spi.util.TestRunners.getTestRunner(TestRunners.java:60) > at org.jboss.arquillian.container.test.spi.util.TestRunners.getTestRunner(TestRunners.java:44) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:158) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:125) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:89) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1230) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) > at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) > at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1071) > at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3815) > at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) > at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:981) > at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) > at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:277) > at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) > at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) > at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) > at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) > at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) > at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) > at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) > at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) > at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) > at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1702) > Any help / resolution is much appreciated. > Attaching required code for reference. JARS list used are as below as not using Maven > arquillian-config-api-1.1.5.Final.jar > arquillian-config-impl-base-1.1.5.Final.jar > arquillian-config-spi-1.1.5.Final.jar > arquillian-container-impl-base-1.1.5.Final.jar > arquillian-container-spi-1.1.5.Final.jar > arquillian-container-test-api-1.1.5.Final.jar > arquillian-container-test-impl-base-1.1.5.Final.jar > arquillian-container-test-spi-1.1.5.Final.jar > arquillian-core-api-1.1.5.Final.jar > arquillian-core-impl-base-1.1.5.Final.jar > arquillian-core-spi-1.1.5.Final.jar > arquillian-junit-container-1.1.5.Final.jar > arquillian-junit-core-1.1.5.Final.jar > arquillian-junit-standalone-1.1.5.Final.jar > arquillian-protocol-jmx-1.1.5.Final.jar > arquillian-protocol-servlet-1.1.5.Final.jar > arquillian-test-api-1.1.5.Final.jar > arquillian-test-impl-base-1.1.5.Final.jar > arquillian-test-spi-1.1.5.Final.jar > arquillian-testenricher-cdi-1.1.5.Final.jar > arquillian-testenricher-ejb-1.1.5.Final.jar > arquillian-testenricher-initialcontext-1.1.5.Final.jar > arquillian-testenricher-resource-1.1.5.Final.jar > arquillian-testng-container-1.1.5.Final.jar > arquillian-testng-core-1.1.5.Final.jar > arquillian-testng-standalone-1.1.5.Final.jar > arquillian-was-remote-8-1.0.0.Final-SNAPSHOT.jar > junit-4.8.1.jar > shrinkwrap-api-1.2.2.jar > shrinkwrap-descriptors-api-base-2.0.0-alpha-5.jar > shrinkwrap-descriptors-api-javaee-2.0.0-alpha-5.jar > shrinkwrap-descriptors-impl-base-2.0.0-alpha-5.jar > shrinkwrap-descriptors-impl-javaee-2.0.0-alpha-5.jar > shrinkwrap-descriptors-spi-2.0.0-alpha-5.jar > shrinkwrap-impl-base-1.2.2.jar > shrinkwrap-spi-1.2.2.jar > Thanks > Saurabh -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 04:52:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 May 2017 04:52:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1532) arquillian warp NoClassDefFoundError In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-1532. ------------------------------- Release Notes Text: Seems to be solved on stackoverflow - user configuration issue Resolution: Won't Fix > arquillian warp NoClassDefFoundError > ------------------------------------ > > Key: ARQ-1532 > URL: https://issues.jboss.org/browse/ARQ-1532 > Project: Arquillian > Issue Type: Bug > Reporter: kelly goedert > Priority: Critical > > When I try to use warp in a deployment that has a jpa datasource in it, an error occurs. I posted this on stackoverflow http://stackoverflow.com/questions/19246684/arquillian-warp-noclassdeffounderror?noredirect=1#comment28533770_19246684 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 04:53:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 May 2017 04:53:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1286) Support Warp on Java EE 5 (Servlets 2.5) compliant containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-1286. ------------------------------- Release Notes Text: Java EE 5 is considered outdated technology by now. I think it's reasonable to close this issue then. Resolution: Won't Fix > Support Warp on Java EE 5 (Servlets 2.5) compliant containers > ------------------------------------------------------------- > > Key: ARQ-1286 > URL: https://issues.jboss.org/browse/ARQ-1286 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Warp is currently focused on Java EE 6 and higher, since it uses {{@WebFilter}} annotation to intercept incoming requests. > We may decide to support Servlets 2.5 containers as well in case there is enough interest (please vote if you are interested). -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 05:00:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 May 2017 05:00:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2088) When test is skipped because of an assumption, Arquillian's test result is passed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-2088. ------------------------------- Resolution: Won't Fix As discussed above - not related to core and fixed in the other project. > When test is skipped because of an assumption, Arquillian's test result is passed > --------------------------------------------------------------------------------- > > Key: ARQ-2088 > URL: https://issues.jboss.org/browse/ARQ-2088 > Project: Arquillian > Issue Type: Enhancement > Components: core > Affects Versions: 1.1.13.Final > Reporter: Matous Jobanek > Assignee: Dipak Pawar > > When you run Arquillian test with an assumption: {{Assume.assumeFalse(true);}} then the test is skipped. The same also say both IDE and maven surefire, but Arquillian's {{TestResult}} retrieved in {{After}} phase contains status Passed. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 05:01:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 May 2017 05:01:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2110) DBUnit Config allowEmptyFields In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410357#comment-13410357 ] Bartosz Majsak commented on ARQ-2110: ------------------------------------- Thank you for the report! > DBUnit Config allowEmptyFields > ------------------------------ > > Key: ARQ-2110 > URL: https://issues.jboss.org/browse/ARQ-2110 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Derek Foster > Assignee: Bartosz Majsak > > The current version of the persistence extension is based on DbUnit 2.4.8, but since then DbUnit has updated to 2.5.3 which has included a feature of allowing empty fields, as opposed to forcing null fields in databases. This feature is quite useful for seeding data. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 05:02:01 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 May 2017 05:02:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2110) DBUnit Config allowEmptyFields In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak resolved ARQ-2110. --------------------------------- Resolution: Done > DBUnit Config allowEmptyFields > ------------------------------ > > Key: ARQ-2110 > URL: https://issues.jboss.org/browse/ARQ-2110 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Derek Foster > Assignee: Bartosz Majsak > > The current version of the persistence extension is based on DbUnit 2.4.8, but since then DbUnit has updated to 2.5.3 which has included a feature of allowing empty fields, as opposed to forcing null fields in databases. This feature is quite useful for seeding data. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 05:02:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 May 2017 05:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2110) DBUnit Config allowEmptyFields In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410357#comment-13410357 ] Bartosz Majsak edited comment on ARQ-2110 at 5/23/17 5:01 AM: -------------------------------------------------------------- Thank you for the report! In fact we are already on 2.5.3 version, just not released yet. was (Author: bmajsak): Thank you for the report! > DBUnit Config allowEmptyFields > ------------------------------ > > Key: ARQ-2110 > URL: https://issues.jboss.org/browse/ARQ-2110 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Derek Foster > Assignee: Bartosz Majsak > > The current version of the persistence extension is based on DbUnit 2.4.8, but since then DbUnit has updated to 2.5.3 which has included a feature of allowing empty fields, as opposed to forcing null fields in databases. This feature is quite useful for seeding data. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 05:04:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 May 2017 05:04:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2066) Support for JUnit 5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410361#comment-13410361 ] Bartosz Majsak commented on ARQ-2066: ------------------------------------- Totally agree with you! This will require new test runner and the work has been started in the community https://developer.jboss.org/message/970675?et=watches.email.thread#970675 > 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 Tue May 23 05:08:01 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 May 2017 05:08:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1868) JVM waits for Spacelift's cached threads to timeout causing its termination delay In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-1868. ------------------------------- Resolution: Out of Date > JVM waits for Spacelift's cached threads to timeout causing its termination delay > --------------------------------------------------------------------------------- > > Key: ARQ-1868 > URL: https://issues.jboss.org/browse/ARQ-1868 > Project: Arquillian > Issue Type: Bug > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Attachments: spacelift_thread_dump.txt > > > In the current implementation of ExecutorService there is this constructor:; > {code} > public ExecutionServiceImpl() { > this.service = Executors.newCachedThreadPool(); > this.scheduledService = Executors.newScheduledThreadPool(1); > } > {code} > JavaDoc for cachedThreadPool says: > {quote} > Threads that have not been used for sixty seconds are terminated and removed from the cache. Thus, a pool that remains idle for long enough will not consume any resources. > {quote} > While this is indeed useful, it seems that even JVM has nothing to do, it waits for these cached threads to timeout (so they are not used some time (60 seconds by default) so they are destroyed eventually) and only after their destruction whole JVM terminates properly. > Please consider to lower the timeout so user does not have to wait or figure out other pooling mechanism. > This issue effects mainly command line tools which hangs without obvious reason and debugging it why is a nightmare. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 05:12:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 May 2017 05:12:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-928) Automation Test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-928. ------------------------------ Resolution: Won't Do > Automation Test > --------------- > > Key: ARQ-928 > URL: https://issues.jboss.org/browse/ARQ-928 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 10:16:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 24 May 2017 10:16:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-501) Error when checking for the invisibility of elements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411374#comment-13411374 ] Matous Jobanek commented on ARQGRA-501: --------------------------------------- Hi, thank you for reporting this. I was trying to reproduce the issue, but without any success - everything is working in my case... However, when I take a look at the code where the exception was thrown - there could be one corner case when this could occur. Here is my proposal how I would fix the issue: https://github.com/arquillian/arquillian-graphene/pull/168 > Error when checking for the invisibility of elements > ---------------------------------------------------- > > Key: ARQGRA-501 > URL: https://issues.jboss.org/browse/ARQGRA-501 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.2.0 > Reporter: Krassimir Valev > > I get the following error message, when waiting for an element to disappear: > {code:java} > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.rangeCheck(ArrayList.java:653) > at java.util.ArrayList.get(ArrayList.java:429) > at org.jboss.arquillian.graphene.enricher.WebElementUtils$3.getTarget(WebElementUtils.java:104) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:189) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:162) > 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.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:209) > 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.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:212) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:208) > at com.sun.proxy.$Proxy316.isDisplayed(Unknown Source) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:585) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:581) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) > {code} > The wait condition looks like this: > {code:java} > return waitGui() > .withTimeout(timeout, TimeUnit.SECONDS) > .pollingEvery(100, TimeUnit.MILLISECONDS) > .ignoring(NoSuchElementException.class, StaleElementReferenceException.class) > .ignoring(InvocationTargetException.class) > .until(ExpectedConditions.invisibilityOfElementLocated(locator)); > {code} > The very same condition used to work with graphene-webdriver 2.0.3.Final and selenium-bom 2.50.1, but it fails now after upgrading to graphene-webdriver 2.2.0 and selenium-bom 3.3.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 10:22:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 24 May 2017 10:22:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-504) Implemented a new method "clickable" in wait API In-Reply-To: References: Message-ID: Matous Jobanek created ARQGRA-504: ------------------------------------- Summary: Implemented a new method "clickable" in wait API Key: ARQGRA-504 URL: https://issues.jboss.org/browse/ARQGRA-504 Project: Arquillian Graphene Issue Type: Enhancement Components: api Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: 2.2.2 It should wait till an element is visible & enabled -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 10:22:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 24 May 2017 10:22:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-504) Implemented a new method "clickable" in wait API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-504: ---------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/166 > Implemented a new method "clickable" in wait API > -------------------------------------------------- > > Key: ARQGRA-504 > URL: https://issues.jboss.org/browse/ARQGRA-504 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.2.2 > > > It should wait till an element is visible & enabled -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 10:36:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 24 May 2017 10:36:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-505) Implement additional API methods for Action operations directly into Graphene class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-505: ---------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/165 > Implement additional API methods for Action operations directly into Graphene class > ----------------------------------------------------------------------------------- > > Key: ARQGRA-505 > URL: https://issues.jboss.org/browse/ARQGRA-505 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.2.2 > > > Methods: > - click() > - doubleClick() > - writeIntoElement() > It should be possible just write: > {code:java} > Graphene.writeIntoElement(element, "my text"); > Graphene.doubleClick(element); > Graphene.click(element); > {code} > Or invoke it directly on {{GrapheneElement}} class -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 10:36:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 24 May 2017 10:36:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-505) Implement additional API methods for Action operations directly into Graphene class In-Reply-To: References: Message-ID: Matous Jobanek created ARQGRA-505: ------------------------------------- Summary: Implement additional API methods for Action operations directly into Graphene class Key: ARQGRA-505 URL: https://issues.jboss.org/browse/ARQGRA-505 Project: Arquillian Graphene Issue Type: Enhancement Components: api Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: 2.2.2 Methods: - click() - doubleClick() - writeIntoElement() It should be possible just write: {code:java} Graphene.writeIntoElement(element, "my text"); Graphene.doubleClick(element); Graphene.click(element); {code} Or invoke it directly on {{GrapheneElement}} class -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 10:46:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 24 May 2017 10:46:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-506) Implement "hover" functionality in Graphene API In-Reply-To: References: Message-ID: Matous Jobanek created ARQGRA-506: ------------------------------------- Summary: Implement "hover" functionality in Graphene API Key: ARQGRA-506 URL: https://issues.jboss.org/browse/ARQGRA-506 Project: Arquillian Graphene Issue Type: Enhancement Components: api Reporter: Matous Jobanek Currently, people face challenges in accessing dropdown submenus. A current implementation of the dropdown submenu hover functionality looks like this: {code:java} @Drone private WebDriver driver; @ArquillianResource private Actions action; driver.get("https://www.bootply.com/render/6FC76YQ4Nh"); Consumer hover = (By by) -> { action.moveToElement(driver.findElement(by)) .perform(); }; hover.accept(By.linkText("Dropdown")); hover.accept(By.linkText("Dropdown Link 5")); hover.accept(By.linkText("Dropdown Submenu Link 5.4")); hover.accept(By.linkText("Dropdown Submenu Link 5.4.1")); {code} An example of the usage of the new Graphene API: {code:java} Graphene.hover(WebElement element) .hover(By by) .hover(WebElement element) .toGrapheneElement() .doubleClick(); {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 10:46:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 24 May 2017 10:46:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-506) Implement "hover" functionality in Graphene API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-506: ---------------------------------- Fix Version/s: 2.2.2 > Implement "hover" functionality in Graphene API > ----------------------------------------------- > > Key: ARQGRA-506 > URL: https://issues.jboss.org/browse/ARQGRA-506 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Fix For: 2.2.2 > > > Currently, people face challenges in accessing dropdown submenus. > A current implementation of the dropdown submenu hover functionality looks like this: > {code:java} > @Drone > private WebDriver driver; > > @ArquillianResource > private Actions action; > > driver.get("https://www.bootply.com/render/6FC76YQ4Nh"); > > Consumer hover = (By by) -> { > action.moveToElement(driver.findElement(by)) > .perform(); > > }; > > hover.accept(By.linkText("Dropdown")); > hover.accept(By.linkText("Dropdown Link 5")); > hover.accept(By.linkText("Dropdown Submenu Link 5.4")); > hover.accept(By.linkText("Dropdown Submenu Link 5.4.1")); > {code} > An example of the usage of the new Graphene API: > {code:java} > Graphene.hover(WebElement element) > .hover(By by) > .hover(WebElement element) > .toGrapheneElement() > .doubleClick(); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 17:03:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Wed, 24 May 2017 17:03:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul updated ARQ-2115: ------------------------------ Fix Version/s: was_1.0.0.next > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Mari?n Macik > Assignee: Gerhard Poul > Fix For: was_1.0.0.next > > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] https://github.com/arquillian/arquillian-container-was/pull/29 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 17:03:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Wed, 24 May 2017 17:03:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul updated ARQ-2115: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Mari?n Macik > Assignee: Gerhard Poul > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] https://github.com/arquillian/arquillian-container-was/pull/29 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 03:19:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 25 May 2017 03:19:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2116) Open DSL to configure DBUnit In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2116: ----------------------------------- Summary: Open DSL to configure DBUnit Key: ARQ-2116 URL: https://issues.jboss.org/browse/ARQ-2116 Project: Arquillian Issue Type: Sub-task Reporter: Bartosz Majsak Currently we only rely on default DBUnit settings which makes it usable only for simple cases such as HSQL DB. For other db engines such as MySQL this is not enough, as we don't have a way to define more specific settings such as DataType, case sensitivity or more db engine specific tweaks. http://dbunit.sourceforge.net/properties.html -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 03:19:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 25 May 2017 03:19:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2116) Open DSL to configure DBUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2116: -------------------------------- Component/s: Extension - Persistence > Open DSL to configure DBUnit > ---------------------------- > > Key: ARQ-2116 > URL: https://issues.jboss.org/browse/ARQ-2116 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Currently we only rely on default DBUnit settings which makes it usable only for simple cases such as HSQL DB. For other db engines such as MySQL this is not enough, as we don't have a way to define more specific settings such as DataType, case sensitivity or more db engine specific tweaks. > http://dbunit.sourceforge.net/properties.html -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 03:19:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 25 May 2017 03:19:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2116) Open DSL to configure DBUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2116: -------------------------------- Fix Version/s: persistence_1.0.0.next > Open DSL to configure DBUnit > ---------------------------- > > Key: ARQ-2116 > URL: https://issues.jboss.org/browse/ARQ-2116 > Project: Arquillian > Issue Type: Sub-task > Reporter: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Currently we only rely on default DBUnit settings which makes it usable only for simple cases such as HSQL DB. For other db engines such as MySQL this is not enough, as we don't have a way to define more specific settings such as DataType, case sensitivity or more db engine specific tweaks. > http://dbunit.sourceforge.net/properties.html -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 04:01:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Thu, 25 May 2017 04:01:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2116) Open DSL to configure DBUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto reassigned ARQ-2116: ------------------------------ Assignee: Alex Soto > Open DSL to configure DBUnit > ---------------------------- > > Key: ARQ-2116 > URL: https://issues.jboss.org/browse/ARQ-2116 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > > Currently we only rely on default DBUnit settings which makes it usable only for simple cases such as HSQL DB. For other db engines such as MySQL this is not enough, as we don't have a way to define more specific settings such as DataType, case sensitivity or more db engine specific tweaks. > http://dbunit.sourceforge.net/properties.html -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 04:02:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Thu, 25 May 2017 04:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2116) Open DSL to configure DBUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-2116 started by Alex Soto. -------------------------------------- > Open DSL to configure DBUnit > ---------------------------- > > Key: ARQ-2116 > URL: https://issues.jboss.org/browse/ARQ-2116 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > > Currently we only rely on default DBUnit settings which makes it usable only for simple cases such as HSQL DB. For other db engines such as MySQL this is not enough, as we don't have a way to define more specific settings such as DataType, case sensitivity or more db engine specific tweaks. > http://dbunit.sourceforge.net/properties.html -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 05:40:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 25 May 2017 05:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2117) Confusing warning message from observer In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2117: ----------------------------------- Summary: Confusing warning message from observer Key: ARQ-2117 URL: https://issues.jboss.org/browse/ARQ-2117 Project: Arquillian Issue Type: Enhancement Components: Base Implementation Reporter: Bartosz Majsak Priority: Minor When observer has one of the arguments null following warning is displayed: {{WARNING [org.jboss.arquillian.core.spi.ObserverMethod] (main) Argument 2 for ArquillianServiceDeployer.doServiceDeploy is null. It won't be invoked.}} It's been introduced for debugging purposes and it's just confusing for the users. We should only display it when {{arquillian.debug=true}} is enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 05:40:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 25 May 2017 05:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2117) Confusing warning message from observer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2117: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/130/files > Confusing warning message from observer > --------------------------------------- > > Key: ARQ-2117 > URL: https://issues.jboss.org/browse/ARQ-2117 > Project: Arquillian > Issue Type: Enhancement > Components: Base Implementation > Reporter: Bartosz Majsak > Assignee: Dipak Pawar > Priority: Minor > > When observer has one of the arguments null following warning is displayed: > {{WARNING [org.jboss.arquillian.core.spi.ObserverMethod] (main) Argument 2 for ArquillianServiceDeployer.doServiceDeploy is null. It won't be invoked.}} > It's been introduced for debugging purposes and it's just confusing for the users. > We should only display it when {{arquillian.debug=true}} is enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 05:40:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 25 May 2017 05:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2117) Confusing warning message from observer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-2117: ----------------------------------- Assignee: Dipak Pawar > Confusing warning message from observer > --------------------------------------- > > Key: ARQ-2117 > URL: https://issues.jboss.org/browse/ARQ-2117 > Project: Arquillian > Issue Type: Enhancement > Components: Base Implementation > Reporter: Bartosz Majsak > Assignee: Dipak Pawar > Priority: Minor > > When observer has one of the arguments null following warning is displayed: > {{WARNING [org.jboss.arquillian.core.spi.ObserverMethod] (main) Argument 2 for ArquillianServiceDeployer.doServiceDeploy is null. It won't be invoked.}} > It's been introduced for debugging purposes and it's just confusing for the users. > We should only display it when {{arquillian.debug=true}} is enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 05:59:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 25 May 2017 05:59:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2117) Confusing warning message from observer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2117: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Confusing warning message from observer > --------------------------------------- > > Key: ARQ-2117 > URL: https://issues.jboss.org/browse/ARQ-2117 > Project: Arquillian > Issue Type: Enhancement > Components: Base Implementation > Reporter: Bartosz Majsak > Assignee: Dipak Pawar > Priority: Minor > > When observer has one of the arguments null following warning is displayed: > {{WARNING [org.jboss.arquillian.core.spi.ObserverMethod] (main) Argument 2 for ArquillianServiceDeployer.doServiceDeploy is null. It won't be invoked.}} > It's been introduced for debugging purposes and it's just confusing for the users. > We should only display it when {{arquillian.debug=true}} is enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 08:21:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 25 May 2017 08:21:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2114) It is easy to reach the GH rate limit when firefox is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2114. ------------------------------- Resolution: Done Pushed upstream in: https://github.com/arquillian/arquillian-extension-drone/commit/c4fda841343d803d9109b77e1785ae85dbc9ae0f https://github.com/arquillian/arquillian-extension-drone/commit/6501fed7e0c7e9e8583cf1376ad44542444fa45c > It is easy to reach the GH rate limit when firefox is used > ---------------------------------------------------------- > > Key: ARQ-2114 > URL: https://issues.jboss.org/browse/ARQ-2114 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.1.1 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.2 > > > When the limit is reached, then you get this error: > {noformat} > 07:48:53 java.lang.RuntimeException: Could not create statement > 07:48:53 at org.jboss.arquillian.junit.Arquillian.methodBlock(Arquillian.java:360) > 07:48:53 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > 07:48:53 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > 07:48:53 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > 07:48:53 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > 07:48:53 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > 07:48:53 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > 07:48:53 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > 07:48:53 at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:205) > 07:48:53 at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431) > 07:48:53 at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55) > 07:48:53 at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:219) > 07:48:53 at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > 07:48:53 at org.junit.rules.RunRules.evaluate(RunRules.java:20) > 07:48:53 at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > 07:48:53 at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:167) > 07:48:53 at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > 07:48:53 at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > 07:48:53 at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > 07:48:53 at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > 07:48:53 at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > 07:48:53 at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > 07:48:53 at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > 07:48:53 Caused by: java.lang.IllegalStateException: Something bad happened when Drone was trying to download and prepare a binary. For more information see the cause. > 07:48:53 at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.checkAndSetBinary(AbstractBinaryHandler.java:61) > 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.getCapabilities(FirefoxDriverFactory.java:107) > 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:73) > 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:39) > 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:127) > 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:38) > 07:48:53 at org.jboss.arquillian.drone.impl.DroneConfigurator$1.createInstance(DroneConfigurator.java:112) > 07:48:53 at org.jboss.arquillian.drone.impl.CachingCallableImpl.call(CachingCallableImpl.java:44) > 07:48:53 at org.jboss.arquillian.core.impl.threading.ThreadedExecutorService$ContextualCallable.call(ThreadedExecutorService.java:89) > 07:48:53 at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 07:48:53 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > 07:48:53 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > 07:48:53 at java.lang.Thread.run(Thread.java:745) > 07:48:53 Caused by: java.lang.IllegalStateException: This is not a JSON Array. > 07:48:53 at com.google.gson.JsonElement.getAsJsonArray(JsonElement.java:106) > 07:48:53 at org.jboss.arquillian.drone.webdriver.binary.downloading.source.GitHubSource.getReleaseForVersion(GitHubSource.java:103) > 07:48:53 at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.downloadAndPrepare(AbstractBinaryHandler.java:161) > 07:48:53 at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.checkAndSetBinary(AbstractBinaryHandler.java:59) > 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.getCapabilities(FirefoxDriverFactory.java:107) > 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:73) > 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:39) > 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:127) > 07:48:53 at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:38) > 07:48:53 at org.jboss.arquillian.drone.impl.DroneConfigurator$1.createInstance(DroneConfigurator.java:112) > 07:48:53 at org.jboss.arquillian.drone.impl.CachingCallableImpl.call(CachingCallableImpl.java:44) > 07:48:53 at org.jboss.arquillian.core.impl.threading.ThreadedExecutorService$ContextualCallable.call(ThreadedExecutorService.java:89) > 07:48:53 at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 07:48:53 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > 07:48:53 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > 07:48:53 at java.lang.Thread.run(Thread.java:745) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 08:30:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 25 May 2017 08:30:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-504) Implemented a new method "clickable" in wait API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-504. --------------------------------- Resolution: Done pushed upstream in: https://github.com/arquillian/arquillian-graphene/commit/366c68bf2191e4f8a1c29c582ac083b372a859a7 > Implemented a new method "clickable" in wait API > -------------------------------------------------- > > Key: ARQGRA-504 > URL: https://issues.jboss.org/browse/ARQGRA-504 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.2.2 > > > It should wait till an element is visible & enabled -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 08:31:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 25 May 2017 08:31:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-505) Implement additional API methods for Action operations directly into Graphene class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-505. --------------------------------- Resolution: Done pushed upstream in: https://github.com/arquillian/arquillian-graphene/commit/f4797703274b4f7fb29cb4a3e674590bd3e3773f > Implement additional API methods for Action operations directly into Graphene class > ----------------------------------------------------------------------------------- > > Key: ARQGRA-505 > URL: https://issues.jboss.org/browse/ARQGRA-505 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.2.2 > > > Methods: > - click() > - doubleClick() > - writeIntoElement() > It should be possible just write: > {code:java} > Graphene.writeIntoElement(element, "my text"); > Graphene.doubleClick(element); > Graphene.click(element); > {code} > Or invoke it directly on {{GrapheneElement}} class -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 08:34:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 25 May 2017 08:34:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-501) Error when checking for the invisibility of elements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411892#comment-13411892 ] Matous Jobanek commented on ARQGRA-501: --------------------------------------- May I ask you for providing a reproducer? So we can add a test case into our test suite and verify that the problem is really fixed. > Error when checking for the invisibility of elements > ---------------------------------------------------- > > Key: ARQGRA-501 > URL: https://issues.jboss.org/browse/ARQGRA-501 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.2.0 > Reporter: Krassimir Valev > > I get the following error message, when waiting for an element to disappear: > {code:java} > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.rangeCheck(ArrayList.java:653) > at java.util.ArrayList.get(ArrayList.java:429) > at org.jboss.arquillian.graphene.enricher.WebElementUtils$3.getTarget(WebElementUtils.java:104) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:189) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:162) > 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.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:209) > 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.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:212) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:208) > at com.sun.proxy.$Proxy316.isDisplayed(Unknown Source) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:585) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:581) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) > {code} > The wait condition looks like this: > {code:java} > return waitGui() > .withTimeout(timeout, TimeUnit.SECONDS) > .pollingEvery(100, TimeUnit.MILLISECONDS) > .ignoring(NoSuchElementException.class, StaleElementReferenceException.class) > .ignoring(InvocationTargetException.class) > .until(ExpectedConditions.invisibilityOfElementLocated(locator)); > {code} > The very same condition used to work with graphene-webdriver 2.0.3.Final and selenium-bom 2.50.1, but it fails now after upgrading to graphene-webdriver 2.2.0 and selenium-bom 3.3.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 08:35:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 25 May 2017 08:35:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-507) Update Arquillian Drone to 2.1.2 In-Reply-To: References: Message-ID: Matous Jobanek created ARQGRA-507: ------------------------------------- Summary: Update Arquillian Drone to 2.1.2 Key: ARQGRA-507 URL: https://issues.jboss.org/browse/ARQGRA-507 Project: Arquillian Graphene Issue Type: Component Upgrade Components: core Affects Versions: 2.2.1 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: 2.2.2 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 25 11:08:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Thu, 25 May 2017 11:08:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2116) Open DSL to configure DBUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-2116: --------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/84 > Open DSL to configure DBUnit > ---------------------------- > > Key: ARQ-2116 > URL: https://issues.jboss.org/browse/ARQ-2116 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > > Currently we only rely on default DBUnit settings which makes it usable only for simple cases such as HSQL DB. For other db engines such as MySQL this is not enough, as we don't have a way to define more specific settings such as DataType, case sensitivity or more db engine specific tweaks. > http://dbunit.sourceforge.net/properties.html -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 26 08:59:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 26 May 2017 08:59:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2116) Open DSL to configure DBUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2116: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Open DSL to configure DBUnit > ---------------------------- > > Key: ARQ-2116 > URL: https://issues.jboss.org/browse/ARQ-2116 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > > Currently we only rely on default DBUnit settings which makes it usable only for simple cases such as HSQL DB. For other db engines such as MySQL this is not enough, as we don't have a way to define more specific settings such as DataType, case sensitivity or more db engine specific tweaks. > http://dbunit.sourceforge.net/properties.html -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 29 12:32:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Mon, 29 May 2017 12:32:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2118) Decouple cleanup and cleanup strategy In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2118: ----------------------------------- Summary: Decouple cleanup and cleanup strategy Key: ARQ-2118 URL: https://issues.jboss.org/browse/ARQ-2118 Project: Arquillian Issue Type: Enhancement Components: Extension - Persistence Reporter: Bartosz Majsak Assignee: Bartosz Majsak As we are bringing more data storage engines in the upcoming 2.0.0 we should decouple cleanup phase and its strategy, as latter at this moment is relevant only for DBUnit -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 30 03:36:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 30 May 2017 03:36:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2101) Improves connection handling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2101: -------------------------------- Priority: Minor (was: Major) > Improves connection handling > ---------------------------- > > Key: ARQ-2101 > URL: https://issues.jboss.org/browse/ARQ-2101 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Priority: Minor > Fix For: persistence_1.0.0.next > > > Improves when connect and disconnect are called, currently connect and disconnect happens once per test method. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 30 03:37:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 30 May 2017 03:37:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2118) Decouple cleanup and cleanup strategy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2118: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/85 > Decouple cleanup and cleanup strategy > ------------------------------------- > > Key: ARQ-2118 > URL: https://issues.jboss.org/browse/ARQ-2118 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > As we are bringing more data storage engines in the upcoming 2.0.0 we should decouple cleanup phase and its strategy, as latter at this moment is relevant only for DBUnit -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 30 03:37:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 30 May 2017 03:37:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2027) JDK 8 with wildfly failing for integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2027: -------------------------------- Fix Version/s: persistence_1.0.0.next > JDK 8 with wildfly failing for integration tests > ------------------------------------------------ > > Key: ARQ-2027 > URL: https://issues.jboss.org/browse/ARQ-2027 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > More details on discuss > http://discuss.arquillian.org/t/help-running-arquillian-persistence-int-tests/307/9 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 30 03:38:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 30 May 2017 03:38:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1942) Duplicate PK encountered when using a ApplyScriptBefore script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-1942. ------------------------------- Resolution: Out of Date > Duplicate PK encountered when using a ApplyScriptBefore script > -------------------------------------------------------------- > > Key: ARQ-1942 > URL: https://issues.jboss.org/browse/ARQ-1942 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6, persistence_1.0.0.Alpha7 > Environment: Windows 8.1 Home, WildFly 8.2.0 Final, jdk1.8.0.40 > Reporter: Dimitrios Kordas > Assignee: Bartosz Majsak > > I am trying to create tests for hibernate under WildFly 8.2.0. > I can successfully create the war using Shrinkwrap, but when Arquillian tries to run the script i provided using the @ApplyScriptBefore annotation hibernate complains about duplicate primary keys even though all keys defined are sequential. > I encounter this error for specific primary keys. For example 1. > If i run the same script (only with an id of 2) multiple times it works. > I have tested the same thing using yaml and json formats and it doesn't work either. > INSERT INTO app_category(id, description, name) VALUES(1, 'entertainment apps', 'Entertainment'); > INSERT INTO app(id,active,fqn,name,app_category_id) VALUES(1,true,'com.facebook','Facebook',1); > INSERT INTO app(id,active,fqn,name,app_category_id) VALUES(2,true,'com.twitter','Twitter',1); > INSERT INTO app(id,active,fqn,name,app_category_id) VALUES(3,true,'com.instagram','Instagram',1); -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 30 03:44:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 30 May 2017 03:44:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1337) Should support multiple datasources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-1337. ------------------------------- Resolution: Duplicate Issue > Should support multiple datasources > ----------------------------------- > > Key: ARQ-1337 > URL: https://issues.jboss.org/browse/ARQ-1337 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Seeding, comparing and applying scripts should be possible for multiple datasources. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 30 03:44:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 30 May 2017 03:44:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1401) Remove dependency on SLF4J In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-1401. ------------------------------- Resolution: Won't Fix Required by DBUnit and is only part of its module as a transitive dependency. > Remove dependency on SLF4J > -------------------------- > > Key: ARQ-1401 > URL: https://issues.jboss.org/browse/ARQ-1401 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Karel Piwko > Assignee: Bartosz Majsak > > SLF4J dependency should be removed/replaced with JUL. Current dependency requires projects to add an slf4j compatible implementation into test dependencies. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 30 03:55:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 30 May 2017 03:55:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1782) @UsingDataSet/@ShouldMatchDataSet always makes test succeed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-1782. ------------------------------- Resolution: Out of Date Fixed in 1.1.5.Final - https://issues.jboss.org/browse/ARQ-1758 > @UsingDataSet/@ShouldMatchDataSet always makes test succeed > ----------------------------------------------------------- > > Key: ARQ-1782 > URL: https://issues.jboss.org/browse/ARQ-1782 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Environment: WildFly 8 CR 2 > Reporter: Nicklas Karlsson > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > {code:xml} > > xsi:schemaLocation=" > http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd"> > 4.0.0 > fi.affecto.marela > arq-concept > 1.0.0-SNAPSHOT > jar > > UTF-8 > chrome > > > > > org.jboss.arquillian > arquillian-bom > 1.1.4.Final > import > pom > > > org.jboss.arquillian.extension > arquillian-drone-bom > 1.3.0.Final > pom > import > > > org.jboss.arquillian.selenium > selenium-bom > 2.41.0 > pom > import > > > > > > junit > junit > 4.11 > test > > > org.jboss.arquillian.junit > arquillian-junit-container > test > > > org.hibernate > hibernate-jpamodelgen > 4.3.5.Final > provided > > > org.jboss.arquillian.graphene > graphene-webdriver > 2.0.2.Final > pom > test > > > org.jboss.arquillian.extension > arquillian-persistence-core > 1.0.0.Alpha7 > > > org.jboss.arquillian.extension > arquillian-persistence-dbunit > 1.0.0.Alpha7 > > > > > arq-wildfly > > > org.jboss.spec > jboss-javaee-7.0 > 1.0.0.Final > pom > provided > > > org.wildfly > wildfly-arquillian-container-remote > 8.1.0.CR2 > test > > > org.jboss.arquillian.protocol > arquillian-protocol-servlet > test > > > > > > > > maven-compiler-plugin > 2.3.2 > > 1.7 > 1.7 > > > > > > src/test/resources > true > > > > > {code} > {code:java} > package fi.affecto.marela.test; > import javax.inject.Inject; > import javax.persistence.EntityManager; > import javax.persistence.PersistenceContext; > import javax.transaction.UserTransaction; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.arquillian.persistence.ShouldMatchDataSet; > import org.jboss.arquillian.persistence.UsingDataSet; > import org.jboss.arquillian.transaction.api.annotation.Transactional; > import org.jboss.shrinkwrap.api.Archive; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.WebArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > import fi.affecto.marela.jpa.Game; > @RunWith(Arquillian.class) > public class PersistenceExtensionTest > { > @Deployment > public static Archive createDeployment() > { > return ShrinkWrap.create(WebArchive.class, "test.war").addPackage(Game.class.getPackage()) > .addAsResource("persistence.xml", "META-INF/persistence.xml") > .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); > } > @PersistenceContext > EntityManager em; > @Inject > UserTransaction utx; > @Test > public void testA() throws Exception > { > Assert.assertNotNull(em); > utx.begin(); > // em.joinTransaction(); > Game g = new Game(); > g.setId(666L); > g.setTitle("x"); > Assert.assertFalse(em.contains(g)); > g = em.merge(g); > Assert.assertTrue(em.contains(g)); > utx.rollback(); > } > > @Test > @Transactional > public void testB() throws Exception > { > Assert.assertNotNull(em); > Game g = new Game(); > g.setId(666L); > g.setTitle("x"); > Assert.assertFalse(em.contains(g)); > g = em.merge(g); > Assert.assertTrue(em.contains(g)); > } > @Test > // @UsingDataSet("games.yml") > // @ShouldMatchDataSet("games-check.yml") > @Transactional > public void testC() throws Exception > { > Assert.assertTrue(false); > } > } > {code} > testC succeeds if the annotations are uncommented. > Furthermore, there is something strange with the em/transactions, the persistence works even if the em doesn't join the transaction and the em complains of a detached instance if merge() is switched for persist() -- This message was sent by Atlassian JIRA (v7.2.3#72005)