September 2013 - arquillian-issues

[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: ------------------------------------ Sounds like a joke to me :), but I will do my best. > 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-282) Create Graphene getting started guide on arquillian.org

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-282?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-282: --------------------------------- Assignee: Juraj Húska (was: Lukáš Fryč) Hey Juraj, could you please review the guide from the grammar perspective? > 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] (ARQ-1385) Drone: resize the PhantomJS window after the start of a test

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1385?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1385: --------------------------------- I would propose lot have this configurable (can be via capability), but also provide a sensible default value: e.g. 1280x1024. > 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-308) Should throw exception if page fragment not instantiable

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-308?page=com.atlassian.jira.plugin... ] Juraj Húska updated ARQGRA-308: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/86 > Should throw exception if page fragment not instantiable > -------------------------------------------------------- > > Key: ARQGRA-308 > URL: https://issues.jboss.org/browse/ARQGRA-308 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Alpha4 > Reporter: Bernard Labno > Assignee: Juraj Húska > Fix For: 2.0.0.Beta1 > > > If page fragment is inner final class then it's not injected into field annotated with @FindBy and no exception is thrown. > Graphene should throw exception that desired class cannot be instantiated. > Right now user spends lots of time debugging and wondering if the selector is wrong. It's hard to find out that it's the "final" word to be blamed here: > public static final class InvitedSupplier -- 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 Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-255?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-255: ----------------------------------- Move the Waiting API to top-level docs (it's too important to be hidden under Graphene utility - we need to link from there): https://docs.jboss.org/author/display/ARQGRA2/Waiting+API > 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] (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: ---------------------------------- Is this a default behavior you need? Or you want to have some value being the default and configurate via webdriver extension? > 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] (ARQ-1472) The precedence for BeforeDroneInstantiated event observation in DroneInstanceCreator is set badly

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1472?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1472. ------------------------------ Assignee: Stefan Miklosovic Resolution: Done > The precedence for BeforeDroneInstantiated event observation in DroneInstanceCreator is set badly > ------------------------------------------------------------------------------------------------- > > Key: ARQ-1472 > URL: https://issues.jboss.org/browse/ARQ-1472 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Beta1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: drone_1.2.0.Beta2 > > > The problem is in DroneInstanceCreator.createDroneInstance method > {code} > public void createDroneInstance(@Observes(precedence = Integer.MAX_VALUE) BeforeDroneInstantiated event) > {code} > Every other observer which listens to this kind of event will be executed before this method (since the precedence, by default 0, is lower then MAX_VALUE for Integer). > If I need to do something BeforeDroneInstantiated when I am observing that event in my custom observer, it has to have higher precedence then this one which is not possible so it results in the fact that my custom BeforeDroneInstantiated observers are treated too late which ends up in funny situation when AfterDroneInstantiated event is fired before other BeforeDroneInstantiated observers take over the controll. -- 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-1472) The precedence for BeforeDroneInstantiated event observation in DroneInstanceCreator is set badly

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1472?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1472: ----------------------------- Component/s: Extension - Drone > The precedence for BeforeDroneInstantiated event observation in DroneInstanceCreator is set badly > ------------------------------------------------------------------------------------------------- > > Key: ARQ-1472 > URL: https://issues.jboss.org/browse/ARQ-1472 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Beta1 > Reporter: Stefan Miklosovic > Fix For: drone_1.2.0.Beta2 > > > The problem is in DroneInstanceCreator.createDroneInstance method > {code} > public void createDroneInstance(@Observes(precedence = Integer.MAX_VALUE) BeforeDroneInstantiated event) > {code} > Every other observer which listens to this kind of event will be executed before this method (since the precedence, by default 0, is lower then MAX_VALUE for Integer). > If I need to do something BeforeDroneInstantiated when I am observing that event in my custom observer, it has to have higher precedence then this one which is not possible so it results in the fact that my custom BeforeDroneInstantiated observers are treated too late which ends up in funny situation when AfterDroneInstantiated event is fired before other BeforeDroneInstantiated observers take over the controll. -- 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-1472) The precedence for BeforeDroneInstantiated event observation in DroneInstanceCreator is set badly

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1472?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1472: ---------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/b48d0884e.... Thanks Stefan! > The precedence for BeforeDroneInstantiated event observation in DroneInstanceCreator is set badly > ------------------------------------------------------------------------------------------------- > > Key: ARQ-1472 > URL: https://issues.jboss.org/browse/ARQ-1472 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: drone_1.2.0.Beta1 > Reporter: Stefan Miklosovic > Fix For: drone_1.2.0.Beta2 > > > The problem is in DroneInstanceCreator.createDroneInstance method > {code} > public void createDroneInstance(@Observes(precedence = Integer.MAX_VALUE) BeforeDroneInstantiated event) > {code} > Every other observer which listens to this kind of event will be executed before this method (since the precedence, by default 0, is lower then MAX_VALUE for Integer). > If I need to do something BeforeDroneInstantiated when I am observing that event in my custom observer, it has to have higher precedence then this one which is not possible so it results in the fact that my custom BeforeDroneInstantiated observers are treated too late which ends up in funny situation when AfterDroneInstantiated event is fired before other BeforeDroneInstantiated observers take over the controll. -- 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-1472) The precedence for BeforeDroneInstantiated event observation in DroneInstanceCreator is set badly

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1472?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1472: ----------------------------- Fix Version/s: drone_1.2.0.Beta2 > The precedence for BeforeDroneInstantiated event observation in DroneInstanceCreator is set badly > ------------------------------------------------------------------------------------------------- > > Key: ARQ-1472 > URL: https://issues.jboss.org/browse/ARQ-1472 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: drone_1.2.0.Beta1 > Reporter: Stefan Miklosovic > Fix For: drone_1.2.0.Beta2 > > > The problem is in DroneInstanceCreator.createDroneInstance method > {code} > public void createDroneInstance(@Observes(precedence = Integer.MAX_VALUE) BeforeDroneInstantiated event) > {code} > Every other observer which listens to this kind of event will be executed before this method (since the precedence, by default 0, is lower then MAX_VALUE for Integer). > If I need to do something BeforeDroneInstantiated when I am observing that event in my custom observer, it has to have higher precedence then this one which is not possible so it results in the fact that my custom BeforeDroneInstantiated observers are treated too late which ends up in funny situation when AfterDroneInstantiated event is fired before other BeforeDroneInstantiated observers take over the controll. -- 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