May 2017 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-2111) Update Selenium to 3.4.0

by Matous Jobanek (JIRA)

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)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2086) Test failures not reported with recent versions of TestNG

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.s... ] 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)

7 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2086) Test failures not reported with recent versions of TestNG

by Dipak Pawar (JIRA)

[ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.s... ] 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/8fba9498efaaec18ce23572fc5a95afb6... * 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/d93431d38e18b2b54e9... * 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/8fba9498efaaec18ce23572fc5a95afb6... * 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/d93431d38e18b2b54e9... * 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)

7 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2086) Test failures not reported with recent versions of TestNG

by Dipak Pawar (JIRA)

[ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.s... ] 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/8fba9498efaaec18ce23572fc5a95afb6... * 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/d93431d38e18b2b54e9... * 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)

7 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2110) DBUnit Config allowEmptyFields

by Derek Foster (JIRA)

[ https://issues.jboss.org/browse/ARQ-2110?page=com.atlassian.jira.plugin.s... ] 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)

7 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2110) DBUnit Config allowEmptyFields

by Derek Foster (JIRA)

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)

7 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2109) EJBInjectionEnricher makes too strong assumptions about JNDI names in the "anonymous" case

by Ladislav Thon (JIRA)

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)

7 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2108) Support for CouchDB seeding in standalone DSL

by Alex Soto (JIRA)

[ https://issues.jboss.org/browse/ARQ-2108?page=com.atlassian.jira.plugin.s... ] Alex Soto resolved ARQ-2108. ---------------------------- Resolution: Done Upstream https://github.com/arquillian/arquillian-extension-persistence/commit/4eb... > 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)

7 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2108) Support for CouchDB seeding in standalone DSL

by Alex Soto (JIRA)

[ https://issues.jboss.org/browse/ARQ-2108?page=com.atlassian.jira.plugin.s... ] 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)

7 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2108) Support for CouchDB seeding in standalone DSL

by Alex Soto (JIRA)

[ https://issues.jboss.org/browse/ARQ-2108?page=com.atlassian.jira.plugin.s... ] 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)

7 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2017