January 2016 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-387) Improve Reporting got from Functional Tests

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-387?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-387: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Improve Reporting got from Functional Tests > ------------------------------------------- > > Key: ARQGRA-387 > URL: https://issues.jboss.org/browse/ARQGRA-387 > Project: Arquillian Graphene > Issue Type: Epic > Reporter: Lukáš Fryč > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-295) Provide more convenient way for Interceptors registration/unregistration

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-295?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-295: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Provide more convenient way for Interceptors registration/unregistration > ------------------------------------------------------------------------- > > Key: ARQGRA-295 > URL: https://issues.jboss.org/browse/ARQGRA-295 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: api, core > Affects Versions: 2.0.0.Alpha4 > Reporter: Juraj Húska > Priority: Minor > Fix For: 2.2-Tracking > > > It would be nice to have a more simple way of registering/unregistering Interceptors. > Currently this is supported: > {code} > GrapheneProxyInstance proxy = (GrapheneProxyInstance) webdriver; > proxy.registerInterceptor(new SearchContextInterceptor()); > {code} > It would be nice to have something like: > {code} > Graphene.registerInterceptor(new SearchContextInterceptor()); > {code} > It will be also good to choose class and method which will be intercepted. > The above mentioned is just minimum. > IMHO it would be awesome to provide way how to register interceptors like it is done in Java EE: > {code} > @Interceptor(MyCustomInterceptor.class) > public void testFooBar() { > ... > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-421) Graphene Interceptors: allow logging of invoked intercepted methods including interceptor chain

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-421?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-421: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Graphene Interceptors: allow logging of invoked intercepted methods including interceptor chain > ----------------------------------------------------------------------------------------------- > > Key: ARQGRA-421 > URL: https://issues.jboss.org/browse/ARQGRA-421 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Lukáš Fryč > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-135) Helpers for writing browser specific code

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-135?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-135: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Helpers for writing browser specific code > ----------------------------------------- > > Key: ARQGRA-135 > URL: https://issues.jboss.org/browse/ARQGRA-135 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: api > Reporter: Lukáš Fryč > Priority: Minor > Fix For: 2.2-Tracking > > > Sometimes people need to deal with interoperability of the code between browsers. > It would be nice if Graphene 2 could provide nice way to handle that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-226) graphene-webdriver-ftest cleanup for reference usage

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-226?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-226: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > graphene-webdriver-ftest cleanup for reference usage > ---------------------------------------------------- > > Key: ARQGRA-226 > URL: https://issues.jboss.org/browse/ARQGRA-226 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Lukáš Fryč > Priority: Trivial > Fix For: 2.2-Tracking > > > {{graphene-webdriver-ftest}} should be used as reference usage for Graphene, thus we need to: > * remove dependency on {{arquillian-test-impl-base}} > * remove dependencies which are commented out > * add comments > ** on depchain - it brings all the dependencies > ** on arquillian-junit-standalone - explain what dependencies might be used instead {{arquillian-{testng,junit}-{standalone,container}}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-377) Make Conditions API more concise when used for if statements and assertions

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-377?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-377: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Make Conditions API more concise when used for if statements and assertions > --------------------------------------------------------------------------- > > Key: ARQGRA-377 > URL: https://issues.jboss.org/browse/ARQGRA-377 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.0.Beta1 > Reporter: Juraj Húska > Fix For: 2.2-Tracking > > > Currently the conditions API looks like: > {code} > new WebElementConditionFactory(webElement).isEnabled().apply(webDriverInstance);{code} > It should be improved to be more concise. > Consider inspiring with *hamcrest* library ([link|https://code.google.com/p/hamcrest/]), which should allow to have conditions API like: > {code} > import static foo.bar.Matchers.*; > public void testEquals() { > WebElement element = browser.findBy(By.tagName("body")); > assertThat(element, isDisplayed()); > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-320) Allow to ask for element visibility without need to check its presence

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-320?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-320: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Allow to ask for element visibility without need to check its presence > ---------------------------------------------------------------------- > > Key: ARQGRA-320 > URL: https://issues.jboss.org/browse/ARQGRA-320 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: api, core, ftest > Affects Versions: 2.0.0.Alpha4 > Reporter: Juraj Húska > Priority: Trivial > Fix For: 2.2-Tracking > > > Currently the only additional method of {{GrapheneElement}} is {{isPresent}}. > It would be nice to add {{isVisible}}. > It should be just matter of mixing {{isPresent}} and {{isDisplayed}} conditions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-460) Introduce Graphene.log page extension, than enables to log to browser console (both, from Java and JavaScript code)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-460?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-460: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Introduce Graphene.log page extension, than enables to log to browser console (both, from Java and JavaScript code) > ------------------------------------------------------------------------------------------------------------------- > > Key: ARQGRA-460 > URL: https://issues.jboss.org/browse/ARQGRA-460 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Fix For: 2.2-Tracking > > > Enable services like XHRInterceptor, RequestGuard and XHRHalter to log via Graphene.log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-390) Improve API

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-390?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-390: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Improve API > ----------- > > Key: ARQGRA-390 > URL: https://issues.jboss.org/browse/ARQGRA-390 > Project: Arquillian Graphene > Issue Type: Epic > Reporter: Lukáš Fryč > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-417) Support for automatic scrolling to element before its usage

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-417?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-417: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Support for automatic scrolling to element before its usage > ----------------------------------------------------------- > > Key: ARQGRA-417 > URL: https://issues.jboss.org/browse/ARQGRA-417 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > Priority: Minor > Fix For: 2.2-Tracking > > > It would be nice if Graphene supports automatic scrolling of browser window to {{WebElement}} / Page Fragment before its is used. > It can be useful for interactions with various popups web components: contextMenu, tooltip, ... > Those components can not be interacted correctly when they are not in the viewport, and thus one needs to scroll to them manually in his test. > It is often problem in CI environment, where tests run on screens with lower resolution (smaller part of the page fit the browser window, and lot of elements are not in the viewport). > My naive implementation of this would look like: > * intercept all calls to {{WebElements}} and PageFragments root elements > * in the interceptor method get the location of the element by: {{Point location = element.getLocation();}} > * a then scroll to it: {{jsExecutor.executeScript("window.scrollTo("" + location.getX() +", " + location.getY() + ")");}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2016