August 2017 - arquillian-issues - Jboss List Archives

[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 updated ARQ-2135: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: transaction_1.0.5 Resolution: Done > 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

[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 updated ARQ-2135: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-transaction/pull/15 > 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 > > 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

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

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-2135: ----------------------------------- Summary: 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 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

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

by Abhijit Humbe (JIRA)

Abhijit Humbe created ARQ-2134: ---------------------------------- Summary: 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-2133) When deployment fails tests with @OperateOnDeployment are still executed

by Evgeniya Evlogieva (JIRA)

Evgeniya Evlogieva created ARQ-2133: --------------------------------------- Summary: When deployment fails tests with @OperateOnDeployment are still executed Key: ARQ-2133 URL: https://issues.jboss.org/browse/ARQ-2133 Project: Arquillian Issue Type: Bug Components: Deployable Containers SPI Affects Versions: 1.1.13.Final Reporter: Evgeniya Evlogieva An application is deployed by the arquillian's @Deployment annotation. When tests are run, only the tests from the first test class (that is executed first) after the deployment, fail directly with 'Deployment failed', the rest of the tests that depend on this deployment are being executed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 9 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/4/17 11:20 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... 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 (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, 9 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/4/17 8:40 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 (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... 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 (but I don't think these scopes should always be equated). 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, 9 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/4/17 8:38 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 (but I don't think these scopes should always be equated). Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though... 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 pages 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 (but I don't think these scopes should always be equated). 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, 9 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/4/17 8:38 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 pages 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 (but I don't think these scopes should always be equated). Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though... 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 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 (but I don't think these scopes should always be equated). 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, 9 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 commented on ARQGRA-382: ------------------------------------------- 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 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 (but I don't think these scopes should always be equated). 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, 9 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