August 2017 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-2136) Add support to preserve original property value using placeholder

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-2136: ----------------------------------- Summary: Add support to preserve original property value using placeholder Key: ARQ-2136 URL: https://issues.jboss.org/browse/ARQ-2136 Project: Arquillian Issue Type: Enhancement Reporter: Bartosz Majsak Priority: Minor https://github.com/arquillian/arquillian-core/pull/122 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2134) Arquillian test only disable web application didnt undeploy application

by Neil Swartz (JIRA)

[ https://issues.jboss.org/browse/ARQ-2134?page=com.atlassian.jira.plugin.s... ] Neil Swartz commented on ARQ-2134: ---------------------------------- It appears that 2.1.0.Beta1 of Arquillian fixes the issue. > Arquillian test only disable web application didnt undeploy application > ----------------------------------------------------------------------- > > Key: ARQ-2134 > URL: https://issues.jboss.org/browse/ARQ-2134 > Project: Arquillian > Issue Type: Bug > Components: JBoss AS Containers > Reporter: Abhijit Humbe > Attachments: simple01892901.tar.gz > > > Arquillian is used to deploy an ear file, run it, and undeploy it from a remote server. When the test runs, it leaves the ear file in the server and it is disabled, but not undeployed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 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 updated ARQ-2086: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/134 > 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)

6 years, 8 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 commented on ARQ-2086: ------------------------------------- There is a new version released, but not published yet to Maven Central. https://bintray.com/cbeust/maven/testng/6.12 With this, I can confirm that all works fine. We have to wait however until the new version of TestNG lands in Maven Central :( > 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)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2134) Arquillian test only disable web application didnt undeploy application

by Neil Swartz (JIRA)

[ https://issues.jboss.org/browse/ARQ-2134?page=com.atlassian.jira.plugin.s... ] Neil Swartz commented on ARQ-2134: ---------------------------------- I found this issue: https://github.com/ingwarsw/arquillian-suite-extension/issues/13 In reading the code I see in ArchiveDeployer that it builds the plan, but does not call "andRemoveUndeployed()" That might be the issue. Could EAP 6.3 have automatically removed the ear, but Wildfly/EAP7 does not? > Arquillian test only disable web application didnt undeploy application > ----------------------------------------------------------------------- > > Key: ARQ-2134 > URL: https://issues.jboss.org/browse/ARQ-2134 > Project: Arquillian > Issue Type: Bug > Components: JBoss AS Containers > Reporter: Abhijit Humbe > Attachments: simple01892901.tar.gz > > > Arquillian is used to deploy an ear file, run it, and undeploy it from a remote server. When the test runs, it leaves the ear file in the server and it is disabled, but not undeployed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-382) Make @InitialPage work for Field

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-382?page=com.atlassian.jira.plugin... ] Karel Piwko commented on ARQGRA-382: ------------------------------------ Vsevolod - haven't read through whole comment but I wanted to flag you can use @InSequence annotation with Arquillian to order tests: http://arquillian.org/guides/getting_started_rinse_and_repeat/ > Make @InitialPage work for Field > -------------------------------- > > Key: ARQGRA-382 > URL: https://issues.jboss.org/browse/ARQGRA-382 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.0.CR1 > Reporter: Karel Piwko > Fix For: 2.0-Tracking > > > While @InitialPage allows to be used on test class field, it does not do anything. > {code} > @InitialPage AddUserPage page; > @Test > void test() { > page.foo() > } > {code} > raises > {code} > java.lang.NullPointerException: null > at com.acme.example.test.DroneTest.addUser(DroneTest.java:35) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-382) Make @InitialPage work for Field

by Vsevolod Golovanov (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-382?page=com.atlassian.jira.plugin... ] Vsevolod Golovanov edited comment on ARQGRA-382 at 8/10/17 8:02 AM: -------------------------------------------------------------------- bq. However, all other fields in tests preserve the state among tests, so Before would be an exception. That seems worrisome, does this imply that the page instances behind \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. -It also mirrors the default Drone instance scope- (Update: I forgot, the default is class scope.) (but I don't think these scopes should always be equated, though class scoped InitialPage certainly makes no sense with a method scoped Drone). Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though... Update. JUnit doesn't have a defined \@Test method execution order. In practice the order often changes between runs. Keeping this in mind, a BeforeClass-like InitialPage doesn't make much sense, unless all the tests somehow guarantee that they won't affect each other, even though they all execute on the same opened page? This is very dubious. TestNG doesn't specify the execution order by default either, but has {{\@Test(priority, dependsOnGroups, dependsOnMethods)}}. I think InitialPage on a field should just always be considered method-scoped (\@Test-scoped). was (Author: vsevolodgolovanov): bq. However, all other fields in tests preserve the state among tests, so Before would be an exception. That seems worrisome, does this imply that the page instances behind \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. -It also mirrors the default Drone instance scope- (Update: I forgot, the default is class scope.) (but I don't think these scopes should always be equated, though class scoped InitialPage certainly makes no sense with a method scoped Drone). Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though... > Make @InitialPage work for Field > -------------------------------- > > Key: ARQGRA-382 > URL: https://issues.jboss.org/browse/ARQGRA-382 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.0.CR1 > Reporter: Karel Piwko > Fix For: 2.0-Tracking > > > While @InitialPage allows to be used on test class field, it does not do anything. > {code} > @InitialPage AddUserPage page; > @Test > void test() { > page.foo() > } > {code} > raises > {code} > java.lang.NullPointerException: null > at com.acme.example.test.DroneTest.addUser(DroneTest.java:35) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-510) cglib is causing warnings in FieldAccessValidatorEnricher

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-510?page=com.atlassian.jira.plugin... ] Matous Jobanek closed ARQGRA-510. --------------------------------- Resolution: Done > cglib is causing warnings in FieldAccessValidatorEnricher > --------------------------------------------------------- > > Key: ARQGRA-510 > URL: https://issues.jboss.org/browse/ARQGRA-510 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.3.0 > Reporter: Vaclav Muzikar > Assignee: Matous Jobanek > Priority: Critical > Fix For: 2.3.1 > > > In Graphene 2.3.0, cglib dependency was updated to version 3.2.5. > When using a Page Object, many warning messages (one for each Page Object) are printed to the log (which could then be literally flooded with those messages). This is probably caused by the cglib update. > {noformat} > Jul 28, 2017 3:52:42 PM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field 'CGLIB$FACTORY_DATA' found in org.test.TestPage$$EnhancerByGraphene$$260509ea. Direct access to fields outside of the declaring class is not allowed. > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-510) cglib is causing warnings in FieldAccessValidatorEnricher

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-510?page=com.atlassian.jira.plugin... ] Matous Jobanek updated ARQGRA-510: ---------------------------------- Fix Version/s: 2.3.1 > cglib is causing warnings in FieldAccessValidatorEnricher > --------------------------------------------------------- > > Key: ARQGRA-510 > URL: https://issues.jboss.org/browse/ARQGRA-510 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.3.0 > Reporter: Vaclav Muzikar > Assignee: Matous Jobanek > Priority: Critical > Fix For: 2.3.1 > > > In Graphene 2.3.0, cglib dependency was updated to version 3.2.5. > When using a Page Object, many warning messages (one for each Page Object) are printed to the log (which could then be literally flooded with those messages). This is probably caused by the cglib update. > {noformat} > Jul 28, 2017 3:52:42 PM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field 'CGLIB$FACTORY_DATA' found in org.test.TestPage$$EnhancerByGraphene$$260509ea. Direct access to fields outside of the declaring class is not allowed. > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2135) TransactionProviderNotFoundException for client side tests

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2135?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak closed ARQ-2135. ------------------------------- > TransactionProviderNotFoundException for client side tests > ---------------------------------------------------------- > > Key: ARQ-2135 > URL: https://issues.jboss.org/browse/ARQ-2135 > Project: Arquillian > Issue Type: Bug > Components: Extension - Transaction > Affects Versions: transaction_1.0.4 > Reporter: Bartosz Majsak > Fix For: transaction_1.0.5 > > > https://github.com/arquillian/arquillian-extension-transaction/issues/14 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues August 2017