May 2013 - arquillian-issues - Jboss List Archives

[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č commented on ARQGRA-301: ----------------------------------- We can enhance the page during a page load - insert a javascript snippet which will register graphene handler. > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-303) Improve failure messages in a fluent waiting API

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-303: --------------------------------- Summary: Improve failure messages in a fluent waiting API Key: ARQGRA-303 URL: https://issues.jboss.org/browse/ARQGRA-303 Project: Arquillian Graphene Issue Type: Feature Request Reporter: Lukáš Fryč Priority: Minor Fix For: 2.0-Tracking Test can currently fail with this message: {code} org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for wrapped: text ('script executed') to be present in element found by By.tagName: title {code} We should: * provide user with current value (last known value before the test failed) * remove the "wrapped:" keyword, since it's misleading -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-299) Setup Graphene tests on SauceLabs

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-299?page=com.atlassian.jira.plugin... ] Work on ARQGRA-299 started by Jan Papousek. > Setup Graphene tests on SauceLabs > --------------------------------- > > Key: ARQGRA-299 > URL: https://issues.jboss.org/browse/ARQGRA-299 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Lukáš Fryč > Assignee: Jan Papousek > Fix For: 2.0.0.Alpha5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-302) Page Fragments injectable by interface

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-302: --------------------------------- Summary: Page Fragments injectable by interface Key: ARQGRA-302 URL: https://issues.jboss.org/browse/ARQGRA-302 Project: Arquillian Graphene Issue Type: Feature Request Reporter: Lukáš Fryč Fix For: 2.Future In order to be able hide implementation details of particular page fragments shipped with a framework, we should favor injection of Page Fragments by interfaces. {code} interface Calendar; class CalendarImpl; @FindBy("calendar") Calendar calendar; {code} The implementation of the calendar can be registered using services mechanism. {code} Builder#service(Calendar.class, CalendarImpl.class); {code} ---- When there are more {{Calendar}} implementations on the classpath registered, the user have either choice of using particular implementation or, preferably, use self-detection built-in into page fragment implementations -> with the knowledge of a root element, they can detect if they are appropriate implementation for given interface. E.g. RichFaces calendar will look a the root element and check whether it has class {{rf-cal}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-224) Page Fragments implementing WebElement delegate interface invocations to Root

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-224?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-224: --------------------------------- Assignee: Lukáš Fryč (was: Juraj Húska) > Page Fragments implementing WebElement delegate interface invocations to Root > ----------------------------------------------------------------------------- > > Key: ARQGRA-224 > URL: https://issues.jboss.org/browse/ARQGRA-224 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Minor > Fix For: 2.0.0.Alpha5 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > {code:java} > public abstract static class InputWithPlaceholder implements WebElement { > > @Root > private WebElement input; > > public String getText() { > return input.getAttribute("value"); > } > > public Color getTextColor() { > return ColorUtils.convertToAWTColor(input.getCssValue("color")); > } > > public String getStyleClass() { > return input.getAttribute("class"); > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-76) Graphene: Setup matrix jobs for browser inter-operability

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-76?page=com.atlassian.jira.plugin.... ] Lukáš Fryč reassigned ARQGRA-76: -------------------------------- Assignee: Jan Papousek (was: Pavol Pitonak) > Graphene: Setup matrix jobs for browser inter-operability > --------------------------------------------------------- > > Key: ARQGRA-76 > URL: https://issues.jboss.org/browse/ARQGRA-76 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: ftest > Reporter: Lukáš Fryč > Assignee: Jan Papousek > Priority: Optional > Fix For: 2.0.0.Alpha5 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-299) Setup Graphene tests on SauceLabs

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-299?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-299: --------------------------------- Assignee: Jan Papousek (was: Pavol Pitonak) > Setup Graphene tests on SauceLabs > --------------------------------- > > Key: ARQGRA-299 > URL: https://issues.jboss.org/browse/ARQGRA-299 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Lukáš Fryč > Assignee: Jan Papousek > Fix For: 2.0.0.Alpha5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

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

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-301?page=com.atlassian.jira.plugin... ] Jan Papousek edited comment on ARQGRA-301 at 5/15/13 4:32 AM: -------------------------------------------------------------- The problem is, we don't have an access to the page generally. Using FirefoxDriver we can use page extensions to attach javascript code to the page, but using other browser the only way is to execute the code you've mentioned via Selenium (JavascriptExecutor), so it can't handle javascript errors before its execution or after page is reload. was (Author: jpapouse): The problem is, we don't have an access to the page generally. Using FirefoxDriver we can use page extensions to attach javascript code to the page, but using other browser the only way is to execute the code you've mentioned via Selenium (JavascriptExecutor), so it can't handle javascript errors before its execution and after page reload. > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

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

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-301?page=com.atlassian.jira.plugin... ] Jan Papousek edited comment on ARQGRA-301 at 5/15/13 4:32 AM: -------------------------------------------------------------- The problem is, we don't have an access to the page generally. Using FirefoxDriver we can use page extensions to attach javascript code to the page, but using other browser the only way is to execute the code you've mentioned via Selenium (JavascriptExecutor), so it can't handle javascript errors before its execution or after page is reloaded. was (Author: jpapouse): The problem is, we don't have an access to the page generally. Using FirefoxDriver we can use page extensions to attach javascript code to the page, but using other browser the only way is to execute the code you've mentioned via Selenium (JavascriptExecutor), so it can't handle javascript errors before its execution or after page is reload. > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

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

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-301?page=com.atlassian.jira.plugin... ] Jan Papousek edited comment on ARQGRA-301 at 5/15/13 4:31 AM: -------------------------------------------------------------- The problem is, we don't have an access to the page generally. Using FirefoxDriver we can use page extensions to attach javascript code to the page, but using other browser the only way is to execute the code you've mentioned via Selenium (JavascriptExecutor), so it can't handle javascript errors before its execution and after page reload. was (Author: jpapouse): The problem is, we don't have an access to the page generally. Using FirefoxDriver we can use page extensions to attach javascript code to the page, but using other browser the only way is to execute the code you've mentioned via Selenium (JavascriptExecutor), so it can't handle javascript error before its execution and after page reload. > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 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 May 2013