April 2016 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-808) Apply the formatter for the GlassFish container adapters

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-808?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak reassigned ARQ-808: ---------------------------------- Assignee: Bartosz Majsak (was: Vineet Reynolds) > Apply the formatter for the GlassFish container adapters > -------------------------------------------------------- > > Key: ARQ-808 > URL: https://issues.jboss.org/browse/ARQ-808 > Project: Arquillian > Issue Type: Task > Components: GlassFish Containers > Reporter: Vineet Reynolds > Assignee: Bartosz Majsak > Priority: Minor > Fix For: glassfish_1.0.0.Final > > > The formatting in the classes of the GlassFish adapters vary from class to class, and sometimes even across lines. We'll need to use a consistent code formatting scheme for this Maven project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1282) TestNG @DataProvider is fully invoked for each record

by Chris Dollar (JIRA)

[ https://issues.jboss.org/browse/ARQ-1282?page=com.atlassian.jira.plugin.s... ] Chris Dollar commented on ARQ-1282: ----------------------------------- I'm using arquillian 1.1.11.Final and the attached workaround isn't working for me. I only get the first element from the data provider and the rest are skipped. Trying to use a @DataProvider normally (without the _provide_ hack) results in the same squared behavior of executions. Does anyone have any other workarounds? Or maybe a clue as what to look at in the arquillian source that might be causing the issue? > TestNG @DataProvider is fully invoked for each record > ----------------------------------------------------- > > Key: ARQ-1282 > URL: https://issues.jboss.org/browse/ARQ-1282 > Project: Arquillian > Issue Type: Bug > Components: JBoss AS Containers > Affects Versions: 1.0.3.Final > Reporter: Karel Cemus > Attachments: ArquillianDataProvider.java, FlightServiceTest.java > > > h2. Expected behavior > TestNG defines @DataProvider annotation to allow single method to perform multiple test cases. Provider method annotated with @DataProvider returns an array of arrays, each containing one test case. These parameters are given to the target method as input parameters. By the definition, the total count of performed test by single method is equal to number of test cases in related data provider. > h2. Actual behavior > Using TestNG under Arquillian framework makes this functionality buggy. Although the client (maven, IDE, etc.) thinks, that the total number of invoked test is correct, it is not. When we take a look into server's log, we can see that for each single test case it invoked full set of all test cases. It means, that in the end the amount of performed tests is equal to expected count squared. Such behaviour is not only slow but also in some cases it doesn't work and it makes tests to fail. > h2. Example > {code:java} > @DataProvider > public Object[][] sumProvider() { > return new Object[][]{ > new Object[]{ 0, 0, 0 }, > new Object[]{ 1, 1, 2 }, > new Object[]{ 1, 5, 6 }, > new Object[]{ 5, 1, 6 } > }; > } > {code} > h3. Expected output in server log > {quote} > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > {quote} > h3. Actual output > {quote} > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQGRA-467) Screenshooter: Tests fail when no Drone contexts exist

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-467?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-467: ----------------------------------- Bonjour, En l'absence de votre correspondant, merci d'adresser votre email Ã jbalunas(a)redhat.com Bien cordialement. -- Dear Sender, In the absence of your contact, please send your email to jbalunas(a)redhat.com Many thanks. -- Lieber Absender, In Abwesenheit Ihrers Kontaktes senden Sie Ihre E-Mail bitte an jbalunas(a)redhat.com Vielen Dank. > Screenshooter: Tests fail when no Drone contexts exist > ------------------------------------------------------ > > Key: ARQGRA-467 > URL: https://issues.jboss.org/browse/ARQGRA-467 > Project: Arquillian Graphene > Issue Type: Bug > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Stefan Miklosovic > Fix For: 2.1.0.Alpha2 > > > https://github.com/arquillian/arquillian-recorder/issues/10 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQGRA-467) Screenshooter: Tests fail when no Drone contexts exist

by Michael Kotten (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-467?page=com.atlassian.jira.plugin... ] Michael Kotten commented on ARQGRA-467: --------------------------------------- I'm using version 2.1.0.CR1 and for me the error isn't gone. I have a project that contains Done/Graphene/Warp tests and ordinary in-container tests with Arquillian. For the in-container tests, the error occurs. The new code {code:java} try { context = GrapheneContext.getContextFor(Default.class); } catch (IllegalStateException ex) { return null; } {code} never returns null for me. This is what i use in my pom.xml. {code:xml} <dependency> <groupId>org.jboss.arquillian.graphene</groupId> <artifactId>arquillian-browser-screenshooter</artifactId> <version>${graphene.version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.arquillian.extension</groupId> <artifactId>arquillian-phantom-driver</artifactId> <version>1.2.1.Final</version> </dependency> <dependency> <groupId>org.jboss.arquillian.graphene</groupId> <artifactId>graphene-webdriver</artifactId> <version>${graphene.version}</version> <type>pom</type> <scope>test</scope> </dependency> {code} > Screenshooter: Tests fail when no Drone contexts exist > ------------------------------------------------------ > > Key: ARQGRA-467 > URL: https://issues.jboss.org/browse/ARQGRA-467 > Project: Arquillian Graphene > Issue Type: Bug > Components: screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Stefan Miklosovic > Fix For: 2.1.0.Alpha2 > > > https://github.com/arquillian/arquillian-recorder/issues/10 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1779) Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1779?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak closed ARQ-1779. ------------------------------- Resolution: Duplicate Issue > Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter > ----------------------------------------------------------------------------------- > > Key: ARQ-1779 > URL: https://issues.jboss.org/browse/ARQ-1779 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Thomas Küstermann > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Forum reference: https://community.jboss.org/message/874117 > The following test case succeeds (green bar) although it should fail: > {code:java} > @RunWith(Arquillian.class) > @DataSource("java:oracleDS") > @Cleanup(phase=TestExecutionPhase.NONE) > @ApplyScriptBefore("deploy-db-functionality.sql") > @ApplyScriptAfter("undeploy-db-functionality.sql") > public class PersistenceIT { > // @Deployment ... > > @Test > @ApplyScriptBefore("trigger-db-functionality.sql") > public void shouldFail() { > Assert.fail("should fail, but doesn't"); > } > } > {code} > Removing class level annotations does not work either: > {code:java} > @Test > @ApplyScriptBefore({ "deploy-db-functionality.sql", "trigger-db-functionality.sql" }) > @ApplyScriptAfter("undeploy-db-functionality.sql") > public void shouldFail() { ... } > {code} > What actually works is to use only one ApplyScriptBefore / ApplyScriptAfter annotation per test, each with only one script to execute. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1817) Ad-hoc H2 java functions are treated as comments

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1817?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1817 started by Bartosz Majsak. ------------------------------------------- > Ad-hoc H2 java functions are treated as comments > ------------------------------------------------ > > Key: ARQ-1817 > URL: https://issues.jboss.org/browse/ARQ-1817 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1815) Unable to locate Oracle Sequence filter

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1815?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak resolved ARQ-1815. --------------------------------- Resolution: Done > Unable to locate Oracle Sequence filter > --------------------------------------- > > Key: ARQ-1815 > URL: https://issues.jboss.org/browse/ARQ-1815 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Blocker > Fix For: persistence_1.0.0.next > > > When trying to define custom table filter using > {{<property name=“customTableFilter”>org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider</property>}} > It's resulting in > {{Unable to find sequence filter for org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider. Using default database sequence filter.}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1815) Unable to locate Oracle Sequence filter

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1815?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak commented on ARQ-1815: ------------------------------------- Pushed upstream [@a91091|https://github.com/arquillian/arquillian-extension-persistence/commit/a91091d26fe9adba31b7edd300e8412b99e01476]. > Unable to locate Oracle Sequence filter > --------------------------------------- > > Key: ARQ-1815 > URL: https://issues.jboss.org/browse/ARQ-1815 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Blocker > Fix For: persistence_1.0.0.next > > > When trying to define custom table filter using > {{<property name=“customTableFilter”>org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider</property>}} > It's resulting in > {{Unable to find sequence filter for org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider. Using default database sequence filter.}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1815) Unable to locate Oracle Sequence filter

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1815?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1815 started by Bartosz Majsak. ------------------------------------------- > Unable to locate Oracle Sequence filter > --------------------------------------- > > Key: ARQ-1815 > URL: https://issues.jboss.org/browse/ARQ-1815 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Blocker > Fix For: persistence_1.0.0.next > > > When trying to define custom table filter using > {{<property name=“customTableFilter”>org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider</property>}} > It's resulting in > {{Unable to find sequence filter for org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider. Using default database sequence filter.}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2026) Client activity failures should have more priority over server activities

by Christian Schulz (JIRA)

Christian Schulz created ARQ-2026: ------------------------------------- Summary: Client activity failures should have more priority over server activities Key: ARQ-2026 URL: https://issues.jboss.org/browse/ARQ-2026 Project: Arquillian Issue Type: Enhancement Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha7 Reporter: Christian Schulz I have noticed multiple times that my warp tests are failing caused by ServerWarpExecutionException. In my research I found out that the DefaultWarpExecutor prefers to show server activity failures over client activity failures. In my opinion client failures should be handled with higher priority, because in most cases the failing client activities is the reason for the server activity failure f.e. with asserts. I would suggest to ignore AssertionErrors from server activities if there is a catched client exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2016