May 2015 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1179) Mark a test so it will only run against certain browsers

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1179?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic commented on ARQ-1179: ---------------------------------------- this could be implemented on Arquillian Governor level, you would have to scan your test class beforehand and skip respective test methods which would be otherwise run by some to-be-injected Drone. > Mark a test so it will only run against certain browsers > -------------------------------------------------------- > > Key: ARQ-1179 > URL: https://issues.jboss.org/browse/ARQ-1179 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Brian Leathem > Fix For: drone_2.0.0.Beta1 > > > It would be useful to be able to annotate a particular test so it will only run when driven by a particular set of browsers. > Some sample use cases: > # Some tests cannot target the incomplete js impl found in html unit. I would mark such tests not to run when htmlunit is the configured browser (in CI for instance) > # Some tests may target non-standard behaviour in certain browsers (older IE versions for instance) and may not make sense to run in all browsers. I would mark such tests not to run only when IE is the configured browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-326) Support for full initialization of outer class instance of a page fragment declared as inner class

by Szymek Pindelski (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-326?page=com.atlassian.jira.plugin... ] Szymek Pindelski edited comment on ARQGRA-326 at 5/29/15 8:47 AM: ------------------------------------------------------------------ hello there, are there any plans to get round to fixing this issue ? It's simetimes handy to use a nested class as a page fragment - for example when a specific section of a web page may occur once or multiple times -- as with JSF <repeat> tag -- and unlike a widget-type page fragment, the section is not reusable (it doesn't make sense to reference it from other page objects / page fragments across your test suite). With and outer class reference you can for instance call your custom assertOnPage() method to ensure you're at the right web page or reuse your enclosing page object's drone reference. was (Author: spine): hello there, are there any plans to get round to fixing this issue ? It's simetimes handy to use a nested class as a page fragment - for example when a specific section of a web page may occur once or multiple times -- as with JSF <repeat> tag? -- and unlike a widget-type page fragment, the section is not reusable (it doesn't make sense to reference it from other page objects / page fragments across your test suite). With and outer class reference you can for instance call your custom assertOnPage() method to ensure you're at the right web page or reuse your enclosing page object's drone reference. > Support for full initialization of outer class instance of a page fragment declared as inner class > -------------------------------------------------------------------------------------------------- > > Key: ARQGRA-326 > URL: https://issues.jboss.org/browse/ARQGRA-326 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Alpha4 > Reporter: Juraj Húska > Priority: Minor > Fix For: 2.0-Tracking > > > If a Page Fragment is declared as inner class, then it can not access the fields of its outer class, as their are not inicialized by Graphene Enrichers, thus are {{null}}. > The possible ugly workaround for such initialization can be: > {code} > if (pageFragment.getClass().getEnclosingClass() != null) { > Field field = pageFragment.getClass().getDeclaredField("this$0"); > field.setAccessible(true); > Object outer = field.get(pageFragment); > enrichRecursively(root, outer); > } > {code} > It should be placed in some utility class, so it can be easily unit tested. > There is one drawback of this method and that is, the outer class can not contain injection point for the inner class, otherwise it will cycle. The inner class can be obtained only dynamically via {{Graphene.createPageFragment}}. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-326) Support for full initialization of outer class instance of a page fragment declared as inner class

by Szymek Pindelski (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-326?page=com.atlassian.jira.plugin... ] Szymek Pindelski commented on ARQGRA-326: ----------------------------------------- hello there, are there any plans to get round to fixing this issue ? It's simetimes handy to use a nested class as a page fragment - for example when a specific section of a web page may occur once or multiple times -- as with JSF <repeat> tag? -- and unlike a widget-type page fragment, the section is not reusable (it doesn't make sense to reference it from other page objects / page fragments across your test suite). With and outer class reference you can for instance call your custom assertOnPage() method to ensure you're at the right web page or reuse your enclosing page object's drone reference. > Support for full initialization of outer class instance of a page fragment declared as inner class > -------------------------------------------------------------------------------------------------- > > Key: ARQGRA-326 > URL: https://issues.jboss.org/browse/ARQGRA-326 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Alpha4 > Reporter: Juraj Húska > Priority: Minor > Fix For: 2.0-Tracking > > > If a Page Fragment is declared as inner class, then it can not access the fields of its outer class, as their are not inicialized by Graphene Enrichers, thus are {{null}}. > The possible ugly workaround for such initialization can be: > {code} > if (pageFragment.getClass().getEnclosingClass() != null) { > Field field = pageFragment.getClass().getDeclaredField("this$0"); > field.setAccessible(true); > Object outer = field.get(pageFragment); > enrichRecursively(root, outer); > } > {code} > It should be placed in some utility class, so it can be easily unit tested. > There is one drawback of this method and that is, the outer class can not contain injection point for the inner class, otherwise it will cycle. The inner class can be obtained only dynamically via {{Graphene.createPageFragment}}. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1955) Screenshot not taken when eception occurs during @Before

by Michael Kotten (JIRA)

Michael Kotten created ARQ-1955: ----------------------------------- Summary: Screenshot not taken when eception occurs during @Before Key: ARQ-1955 URL: https://issues.jboss.org/browse/ARQ-1955 Project: Arquillian Issue Type: Bug Components: Extension - Recorder Affects Versions: recorder_1.0.0.Final Reporter: Michael Kotten If a test fails with an exception during the @Before method, there is no screenshot taken, even with takeWhenTestFailed=true. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1954) Support @Rule enrichement

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1954: -------------------------------- Summary: Support @Rule enrichement Key: ARQ-1954 URL: https://issues.jboss.org/browse/ARQ-1954 Project: Arquillian Issue Type: Feature Request Components: Base Implementation Affects Versions: 1.1.8.Final Reporter: Karel Piwko Arquillian should by default enrich JUnit @Rule statements. Similarly to https://github.com/aerogear/aerogear-testing-tools/blob/master/arquillian... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on ARQ-1952: ------------------------------------ [~ppitonak] does anyone in your group have feedback on this Warp issue? > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: Pëtr Andreev > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-470) Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-470?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-470: --------------------------------- Assignee: Matous Jobanek > Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent > --------------------------------------------------------------------------------------------------- > > Key: ARQGRA-470 > URL: https://issues.jboss.org/browse/ARQGRA-470 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha2 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.1-Tracking > > > There in the org.jboss.arquillian.graphene:graphene-parent pom is defined a dependency: > {code:xml} > <dependency> > <groupId>org.jboss.logging</groupId> > <artifactId>jboss-logging</artifactId> > <version>${version.jboss.logging}</version> > </dependency> > {code} > however the variable {{version.jboss.logging}} is not defined neither it this pom nor in the parent pom. > see: > [org.jboss.arquillian.graphene:graphene-parent:2.1.0.Alpha2|https://repo1....] > [github|https://github.com/arquillian/arquillian-graphene/blob/master/pom.xml] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-470) Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-470?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-470: ----------------------------------- Thanks Matous! > Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent > --------------------------------------------------------------------------------------------------- > > Key: ARQGRA-470 > URL: https://issues.jboss.org/browse/ARQGRA-470 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha2 > Reporter: Matous Jobanek > Fix For: 2.1-Tracking > > > There in the org.jboss.arquillian.graphene:graphene-parent pom is defined a dependency: > {code:xml} > <dependency> > <groupId>org.jboss.logging</groupId> > <artifactId>jboss-logging</artifactId> > <version>${version.jboss.logging}</version> > </dependency> > {code} > however the variable {{version.jboss.logging}} is not defined neither it this pom nor in the parent pom. > see: > [org.jboss.arquillian.graphene:graphene-parent:2.1.0.Alpha2|https://repo1....] > [github|https://github.com/arquillian/arquillian-graphene/blob/master/pom.xml] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-470) Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-470?page=com.atlassian.jira.plugin... ] Matous Jobanek resolved ARQGRA-470. ----------------------------------- Resolution: Done > Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent > --------------------------------------------------------------------------------------------------- > > Key: ARQGRA-470 > URL: https://issues.jboss.org/browse/ARQGRA-470 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha2 > Reporter: Matous Jobanek > Fix For: 2.1-Tracking > > > There in the org.jboss.arquillian.graphene:graphene-parent pom is defined a dependency: > {code:xml} > <dependency> > <groupId>org.jboss.logging</groupId> > <artifactId>jboss-logging</artifactId> > <version>${version.jboss.logging}</version> > </dependency> > {code} > however the variable {{version.jboss.logging}} is not defined neither it this pom nor in the parent pom. > see: > [org.jboss.arquillian.graphene:graphene-parent:2.1.0.Alpha2|https://repo1....] > [github|https://github.com/arquillian/arquillian-graphene/blob/master/pom.xml] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-470) Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-470?page=com.atlassian.jira.plugin... ] Matous Jobanek commented on ARQGRA-470: --------------------------------------- PR sent and merged https://github.com/arquillian/arquillian-graphene/pull/131 > Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent > --------------------------------------------------------------------------------------------------- > > Key: ARQGRA-470 > URL: https://issues.jboss.org/browse/ARQGRA-470 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha2 > Reporter: Matous Jobanek > Fix For: 2.1-Tracking > > > There in the org.jboss.arquillian.graphene:graphene-parent pom is defined a dependency: > {code:xml} > <dependency> > <groupId>org.jboss.logging</groupId> > <artifactId>jboss-logging</artifactId> > <version>${version.jboss.logging}</version> > </dependency> > {code} > however the variable {{version.jboss.logging}} is not defined neither it this pom nor in the parent pom. > see: > [org.jboss.arquillian.graphene:graphene-parent:2.1.0.Alpha2|https://repo1....] > [github|https://github.com/arquillian/arquillian-graphene/blob/master/pom.xml] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2015