September 2013 - arquillian-issues

[JBoss JIRA] (ARQGRA-351) InFrame does not take LocationStrategies into consideration

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-351?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-351. ------------------------------- Resolution: Rejected The implementation works as expected, ftest commited here: https://github.com/arquillian/arquillian-graphene/commit/4317b6aa0879b3b8... > InFrame does not take LocationStrategies into consideration > ----------------------------------------------------------- > > Key: ARQGRA-351 > URL: https://issues.jboss.org/browse/ARQGRA-351 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 2.0.0.Beta1 > > > Change: > https://github.com/arquillian/arquillian-graphene/commit/cf007d86dc917642... > Use: > https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/ma... > or perhaps: > https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/ma... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-358) GrapheneContextImpl.getPageExtensionInstallatorProvider() returns null

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-358?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-358: ------------------------------ Fix Version/s: 2.1-Tracking (was: 2.0.0.Beta1) > GrapheneContextImpl.getPageExtensionInstallatorProvider() returns null > ---------------------------------------------------------------------- > > Key: ARQGRA-358 > URL: https://issues.jboss.org/browse/ARQGRA-358 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Lukáš Fryč > Fix For: 2.1-Tracking > > > https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/ma... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-365) Invalid verification of element presence with css locator

by Michal Vanco (JIRA)

Michal Vanco created ARQGRA-365: ----------------------------------- Summary: Invalid verification of element presence with css locator Key: ARQGRA-365 URL: https://issues.jboss.org/browse/ARQGRA-365 Project: Arquillian Graphene Issue Type: Bug Affects Versions: 2.0.0.Alpha5 Reporter: Michal Vanco Fix For: 2.0.0.Beta1 I have a page fragment with some element mapped with @FindBy(css='...'), this element is available after some operation in fragment. When I call Graphene.waitGui().until().element(element).is().present(), it fails on NoSuchElementException. Note that this fails with css locator, but works fine with xpath locator. At first, element is trying to de-reference (with failure) and then call toString(), related code is at: https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/ma... See the stacktrace at: https://gist.github.com/michalvanco/2fd53306a983ed386b02 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1385) Drone: resize the PhantomJS window after the start of a test

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1385?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1385: ---------------------------------- Thinking about that, isn't this valid to all WebDriver browsers? This could be nice default Enhancer aiui. > Drone: resize the PhantomJS window after the start of a test > ------------------------------------------------------------ > > Key: ARQ-1385 > URL: https://issues.jboss.org/browse/ARQ-1385 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha2 > Reporter: Lukáš Fryč > Labels: starter > > The PhantomJS starts with incredibly small window, so it prevents to run lot of the tests where elements aren't shown in the initial viewport. > We can use this instructions selectively for PhantomJS to make it work: > https://github.com/richfaces/richfaces5/blob/master/build/build-resources... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-351) InFrame does not take LocationStrategies into consideration

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-351?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-351: --------------------------------- Assignee: Lukáš Fryč > InFrame does not take LocationStrategies into consideration > ----------------------------------------------------------- > > Key: ARQGRA-351 > URL: https://issues.jboss.org/browse/ARQGRA-351 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 2.0.0.Beta1 > > > Change: > https://github.com/arquillian/arquillian-graphene/commit/cf007d86dc917642... > Use: > https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/ma... > or perhaps: > https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/ma... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-338) Finish JavaDoc for API and SPI

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-338?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-338: ------------------------------ Summary: Finish JavaDoc for API and SPI (was: Finish JavaDoc for API and SPI and upload it online) > Finish JavaDoc for API and SPI > ------------------------------ > > Key: ARQGRA-338 > URL: https://issues.jboss.org/browse/ARQGRA-338 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 2.0.0.Beta1 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-338) Finish JavaDoc for API and SPI

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-338?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-338. ------------------------------- Resolution: Done > Finish JavaDoc for API and SPI > ------------------------------ > > Key: ARQGRA-338 > URL: https://issues.jboss.org/browse/ARQGRA-338 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 2.0.0.Beta1 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-364) Allow extensibility of GrapheneElement

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-364: --------------------------------- Summary: Allow extensibility of GrapheneElement Key: ARQGRA-364 URL: https://issues.jboss.org/browse/ARQGRA-364 Project: Arquillian Graphene Issue Type: Enhancement Reporter: Lukáš Fryč Implement GrapheneElement#as(Class<?> type) method which will do a coercion to the given type. If the given type is not implemented by wrapped WebElement, the service which implements this method will be called instead. This allows for simple extensibility mechanism: {code} @FindBy GrapheneElement element; @Test test() { element.as(ValidableElement).checkValidity(); } {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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-282) Create Graphene getting started guide on arquillian.org

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-282?page=com.atlassian.jira.plugin... ] Juraj Húska commented on ARQGRA-282: ------------------------------------ I have tried to fix what I could. > Create Graphene getting started guide on arquillian.org > ------------------------------------------------------- > > Key: ARQGRA-282 > URL: https://issues.jboss.org/browse/ARQGRA-282 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: doc > Reporter: Juraj Húska > Assignee: Juraj Húska > Fix For: 2.0.0.Beta1 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > Possible option is to alter functional testing guide which is here: > http://arquillian.org/guides/functional_testing_using_drone/ -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-361) Reimplement WebElement/PageFragment/ElementWrapper Enrichers to have one enrichment base which delegates to factories

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-361?page=com.atlassian.jira.plugin... ] Juraj Húska commented on ARQGRA-361: ------------------------------------ It would be vital addition indeed. I am just wondering how do you imagine the {{PageFragmentRegistry}} registration API. Where and how an user can register their fragments ? > Reimplement WebElement/PageFragment/ElementWrapper Enrichers to have one enrichment base which delegates to factories > --------------------------------------------------------------------------------------------------------------------- > > Key: ARQGRA-361 > URL: https://issues.jboss.org/browse/ARQGRA-361 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Lukáš Fryč > > All of these enrichers scans for FindBy annotations: > * [WebElementEnricher|https://github.com/arquillian/arquillian-graphene/blob...] > * [PageFragmentEnricher|https://github.com/arquillian/arquillian-graphene/bl...] > * [WebElementWrapperEnricher|https://github.com/arquillian/arquillian-graphe...] > That leads into disambiguity since the solution is not readable. It also brings code duplication. > ---- > The suggested refactoring should lead into one enricher, which delegates to particular factories. > It will evaluate which type of injection should happen: > * interface / abstract class (needs to check newly created registry for implementation) > ** this is suitable for WebElement or GrapheneElement injections (GrapheneElement needs to be refactored to interface) > ** it's also case of page fragments with interface and implementation > * element wrapper: MyWrapper(WebElement) > ** this is case of e.g. Select(WebElement) > * page fragment implementation > When interface / abstract class doesn't find suitable implementation or it is a final class, exception should be thrown. -- 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, 7 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 September 2013