January 2016 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-407) Document WebDriverWait API

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-407?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-407: ------------------------------ Sprint: Graphene 2.0.1 (was: Graphene 2.0.1, Graphene 2.0.2) > Document WebDriverWait API > -------------------------- > > Key: ARQGRA-407 > URL: https://issues.jboss.org/browse/ARQGRA-407 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Lukáš Fryč > Priority: Critical > Fix For: 2.0-Tracking > > > https://github.com/arquillian/arquillian-graphene/blob/2.0.0.Final/api/sr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-395) Graphene.guardAjax() doesn't work correctly in IE

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-395?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-395: ------------------------------ Sprint: Graphene 2.0.1 (was: Graphene 2.0.1, Graphene 2.0.2) > Graphene.guardAjax() doesn't work correctly in IE > ------------------------------------------------- > > Key: ARQGRA-395 > URL: https://issues.jboss.org/browse/ARQGRA-395 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.0.CR2 > Environment: IE 7, 8, 9 > Reporter: Jan Dosoudil > Fix For: 2.0-Tracking > > > I have jsf page h:commandButton with f:ajax. Testing with Graphene.guardAjax(button).click(); works with Firefox, htmlUnit, phantomjs but doesn't with Internet Explorer (7, 8, 9). Internet explorer calls onclick function but without return false which causes full page submit. > button.click() works ok. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-396) Check/review JDF web-UI quickstarts for Graphene reference usage

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-396?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-396: ------------------------------ Sprint: Graphene 2.0.1 Sprint 1 (was: Graphene 2.0.1 Sprint 1, Graphene 2.0.2) > Check/review JDF web-UI quickstarts for Graphene reference usage > ---------------------------------------------------------------- > > Key: ARQGRA-396 > URL: https://issues.jboss.org/browse/ARQGRA-396 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Lukáš Fryč > Assignee: Oliver Kišš > Fix For: 2.0-Tracking > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-464) @Page injection should support parameter injection

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-464?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-464: --------------------------------- Assignee: (was: Karel Piwko) > @Page injection should support parameter injection > -------------------------------------------------- > > Key: ARQGRA-464 > URL: https://issues.jboss.org/browse/ARQGRA-464 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.1.0.Alpha1 > Reporter: Karel Piwko > Fix For: 2.1-Tracking > > > Graphene should support @Page injection even for parameter injection in test methods. This would make test case much more compact. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-380) Debugging in Eclipse throw InvocationException when inspecting fields enriched by Graphene

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-380?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-380: --------------------------------- Assignee: (was: Juraj Húska) > Debugging in Eclipse throw InvocationException when inspecting fields enriched by Graphene > ------------------------------------------------------------------------------------------ > > Key: ARQGRA-380 > URL: https://issues.jboss.org/browse/ARQGRA-380 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.0.Beta2 > Reporter: Juraj Húska > Fix For: 2.1-Tracking > > > During debugging in Eclipse, when inspecting the values of the fields which are enriched by Graphene, an {{InvocationException}} is thrown. > We should investigate why it is so, and improve it if it is feasible. It can enhance the usability. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-453) takeOnEveryAction acts only on methods from WebDriver object, add support for PO & PF & WebElement

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-453?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-453: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > takeOnEveryAction acts only on methods from WebDriver object, add support for PO & PF & WebElement > -------------------------------------------------------------------------------------------------- > > Key: ARQGRA-453 > URL: https://issues.jboss.org/browse/ARQGRA-453 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core, screenshooter > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj Húska > Assignee: Juraj Húska > Fix For: 2.2-Tracking > > > {{takeOnEveryAction}} now takes screenshot only when a method on {{WebDriver}} object is invoked. > To achieve something like visual testing, it would need to support also intercepting methods invoked on: > * {{WebElement}} > * Page objects > * Page fragments -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 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 Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-326?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-326: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > 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.2-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.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-301) Support for assertions on errors and console output

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-301?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-301: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Support for assertions on errors and console output > --------------------------------------------------- > > Key: ARQGRA-301 > URL: https://issues.jboss.org/browse/ARQGRA-301 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Brian Leathem > Fix For: 2.2-Tracking > > > In a recent Graphene based test [\[1\]|https://github.com/richfaces/components/commit/857f73bbf87f495e36c33072c5c4415d4b02be10#L1R85] I registered a window.onerror listener to store errors in the DOM for later retrieval by Graphene/Selenium for use in an assertion. > It would be great if Graphene could do this automatically, providing an API for accessing both error messages, and console output. > [1] https://github.com/richfaces/components/commit/857f73bbf87f495e36... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-42) Reduce logging levels

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-42?page=com.atlassian.jira.plugin.... ] Lukáš Fryč updated ARQGRA-42: ----------------------------- Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Reduce logging levels > --------------------- > > Key: ARQGRA-42 > URL: https://issues.jboss.org/browse/ARQGRA-42 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: junit, testng > Affects Versions: 1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Optional > Fix For: 2.2-Tracking > > > Ajocado outputs many debug information under INFO logging level. This level should be reduced to debug or even debug/fine. > It makes execution of the test slower and this information is not required until debugging. > It manifest namely with JUnit which redirects test output to console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-434) Browser screenshooter acts only on @Default Drone

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-434?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-434: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Browser screenshooter acts only on @Default Drone > ------------------------------------------------- > > Key: ARQGRA-434 > URL: https://issues.jboss.org/browse/ARQGRA-434 > Project: Arquillian Graphene > Issue Type: Bug > Components: screenshooter > Affects Versions: 2.1-Tracking > Reporter: Stefan Miklosovic > Assignee: Juraj Húska > Fix For: 2.2-Tracking > > > Browser screenshooter acts only on Drone instances which do not have any qualifier but @Default since current implementation does this check: > {code} > GrapheneContext.getContextFor(Default.class) > {code} > This usage prevents user to use screenshooter in multibrowser scenarios like having Android browser and ordinary Firefox browser in one test class since they can (and must) be differentiated by additional qualifier put on @Drone instances. > Check should be done on instance level and not on qualifier level - meaning we should take context of Drone with ordinary (not mobile) browser which can have any qualifier possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2016