September 2013 - arquillian-issues

[JBoss JIRA] (ARQGRA-369) CLONE - Stage artifacts to Maven repository

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-369: --------------------------------- Summary: CLONE - Stage artifacts to Maven repository Key: ARQGRA-369 URL: https://issues.jboss.org/browse/ARQGRA-369 Project: Arquillian Graphene Issue Type: Sub-task Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 2.0.0.Alpha5 -- 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-367) CLONE - Run QUnit tests manually

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-367: --------------------------------- Summary: CLONE - Run QUnit tests manually Key: ARQGRA-367 URL: https://issues.jboss.org/browse/ARQGRA-367 Project: Arquillian Graphene Issue Type: Sub-task Affects Versions: 2.0.0.Alpha5 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 2.0.0.Alpha5 -- 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-370) CLONE - Announce a release

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-370: --------------------------------- Summary: CLONE - Announce a release Key: ARQGRA-370 URL: https://issues.jboss.org/browse/ARQGRA-370 Project: Arquillian Graphene Issue Type: Sub-task Reporter: Lukáš Fryč Assignee: Aslak Knutsen Fix For: 2.0.0.Alpha5 -- 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-343) Announce a release

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-343?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-343. ------------------------------- Resolution: Done > Announce a release > ------------------ > > Key: ARQGRA-343 > URL: https://issues.jboss.org/browse/ARQGRA-343 > Project: Arquillian Graphene > Issue Type: Sub-task > Reporter: Lukáš Fryč > Assignee: Aslak Knutsen > Fix For: 2.0.0.Alpha5 > > -- 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 Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-365?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-365: ----------------------------------- After investigation, me and Michal found out that Xpath locator worked because it was referenced by root. The page which referenced element that wasn't found, was injected as Page Fragment: @FindBy(id = "root"). But the element wasn't under the DOM tree under "root". That's why XPath was able to find it and CSS wasn't. > 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 > Assignee: Lukáš Fryč > Fix For: 2.0-Tracking > > > 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] (ARQGRA-365) Invalid verification of element presence with css locator

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-365?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-365. ------------------------------- Fix Version/s: (was: 2.0-Tracking) Resolution: Rejected Rejecting as this is code mistake. > 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 > Assignee: Lukáš Fryč > > 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] (ARQGRA-255) Update documentation for Alpha3, Alpha4 and Alpha5 features

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-255?page=com.atlassian.jira.plugin... ] Juraj Húska edited comment on ARQGRA-255 at 9/10/13 9:13 AM: ------------------------------------------------------------- Sure thing Lukas. Here are the changes I have identified. The striked ones are already incorporated in the doc: * -deprecation of {{guardXhr}}- * -create new subpage for Graphene Interceptors and provided small example of interceptor defining and registering- * {{GrapheneElement}} and its methods {{isPresent}}, {{fire}} - include {{attribute().value()}}, {{present()}} * fluent API of waits - examples, Graphene.element deprecated * request guards filters - ARQGRA-275 * -injecting {{WebElement}} wrappers - ARQGRA-258 - e.g. Select support- * -create sub page for Graphene {{@FindBy}} and JQuery support, supporting Selenium features like {{FindBys}}, {{How}}- * -Automatically infer ID locator from field name annotated just by {{@FindBy}}- * -Page Fragments can be created dynamically- * {{GrapheneContext.getProxy}} does not exist anymore - one static context * It is possible to have multiple {{WebDriver}} instances in one test to achieve multiple windows support - ARQGRA-72 * -Page Objects and Page Fragments can be declared as nested classes- * -Page Fragments do not need to have {{@Root}} annotated field- * -Page Fragments can be nested in other fragments- * -Injecting Lists annotated with FindBy- * Mention StaleElement interceptor * -{{@InFrame}} annotation behavior- Changes I would like to gather more info about: * {{RequestGuard.setMaximumCallbackTimeout}} * Expose LocalStorage and SessionStorage enrichments directly - ARQGRA-254 was (Author: jhuska): Sure thing Lukas. Here are the changes I have identified. The striked ones are already incorporated in the doc: * -deprecation of {{guardXhr}}- * -create new subpage for Graphene Interceptors and provided small example of interceptor defining and registering- * {{GrapheneElement}} and its methods {{isPresent}}, {{fire}} - include {{attribute().value()}}, {{present()}} * fluent API of waits - examples, Graphene.element deprecated * request guards filters - ARQGRA-275 * -injecting {{WebElement}} wrappers - ARQGRA-258 - e.g. Select support- * -create sub page for Graphene {{@FindBy}} and JQuery support, supporting Selenium features like {{FindBys}}, {{How}}- * -Automatically infer ID locator from field name annotated just by {{@FindBy}}- * -Page Fragments can be created dynamically- * {{GrapheneContext.getProxy}} does not exist anymore - one static context * It is possible to have multiple {{WebDriver}} instances in one test to achieve multiple windows support - ARQGRA-72 * -Page Objects and Page Fragments can be declared as nested classes- * -Page Fragments do not need to have {{@Root}} annotated field- * -Page Fragments can be nested in other fragments- * -Injecting Lists annotated with FindBy- * Mention StaleElement interceptor * {{@InFrame}} annotation behavior Changes I would like to gather more info about: * {{RequestGuard.setMaximumCallbackTimeout}} * Expose LocalStorage and SessionStorage enrichments directly - ARQGRA-254 > Update documentation for Alpha3, Alpha4 and Alpha5 features > ----------------------------------------------------------- > > Key: ARQGRA-255 > URL: https://issues.jboss.org/browse/ARQGRA-255 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Priority: Critical > Fix For: 2.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 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, 7 months

1
0
0 / 0

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

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-365?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-365: ------------------------------ Fix Version/s: 2.0-Tracking (was: 2.0.0.Beta1) > 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 > Assignee: Lukáš Fryč > Fix For: 2.0-Tracking > > > 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] (ARQGRA-365) Invalid verification of element presence with css locator

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-365?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-365: ----------------------------------- I have tried to reproduce the issue according to provided information: https://gist.github.com/lfryc/6509066 I had no success to reproduce it. > 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 > Assignee: Lukáš Fryč > 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] (ARQGRA-255) Update documentation for Alpha3, Alpha4 and Alpha5 features

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-255?page=com.atlassian.jira.plugin... ] Juraj Húska edited comment on ARQGRA-255 at 9/10/13 8:53 AM: ------------------------------------------------------------- * Graphene Page Object location encapsulation docs added * Graphene Utility class doc page refactored and updated - duplicates for wait, request guards API removed, referenced for top lvl pages added * Location Strategy added was (Author: jhuska): * Graphene Page Object location encapsulation docs added * Graphene Utility class doc page refactored and updated - duplicates for wait, request guards API removed, referenced for top lvl pages added > Update documentation for Alpha3, Alpha4 and Alpha5 features > ----------------------------------------------------------- > > Key: ARQGRA-255 > URL: https://issues.jboss.org/browse/ARQGRA-255 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Priority: Critical > Fix For: 2.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 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, 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