[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 closed ARQ-1472.
----------------------------
> 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
11 years, 4 months
[JBoss JIRA] (ARQ-1475) Enhancer does not allow access to real instance
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1475?page=com.atlassian.jira.plugin.s... ]
Karel Piwko closed ARQ-1475.
----------------------------
> Enhancer does not allow access to real instance
> -----------------------------------------------
>
> Key: ARQ-1475
> URL: https://issues.jboss.org/browse/ARQ-1475
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_1.2.0.Beta1
> Reporter: Karel Piwko
> Assignee: Karel Piwko
> Fix For: drone_1.2.0.Beta2
>
>
> Enhancer API does not support getting real instance to be enhanced and droneType, which reflect field or parameter type, is misleading, because it does not reflect real instance type.
> This might be a problem, especially if enhancer will report that it can't enhance an instance only because user injected it into WebDriver type, which is a super type, that might not support given feature.
--
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
11 years, 4 months
[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 closed ARQ-1385.
----------------------------
> 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č
> Assignee: Karel Piwko
> Labels: starter
> Fix For: drone_1.2.0.Beta2
>
>
> 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:
> {code}
> org.openqa.selenium.ElementNotVisibleException: Error Message => 'Element is not currently visible and may not be manipulated' caused by Request => {"headers":{"Accept":"application/json, image/png","Connection":"Keep-Alive","Content-Length":"27","Content-Type":"application/json; charset=utf-8","Host":"localhost:24743"},"httpVersion":"1.1","method":"POST","post":"{\"id\":\":wdc:1378914555889\"}","url":"/click","urlParsed":{"anchor":"","query":"","file":"click","directory":"/","path":"/click","relative":"/click","port":"","host":"","password":"","user":"","userI
> {code}
> 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
11 years, 4 months
[JBoss JIRA] (ARQ-951) Drone: Setup Matrix jobs for browser support
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-951?page=com.atlassian.jira.plugin.sy... ]
Karel Piwko updated ARQ-951:
----------------------------
Original Estimate: 2 days
Remaining Estimate: 2 days
> Drone: Setup Matrix jobs for browser support
> --------------------------------------------
>
> Key: ARQ-951
> URL: https://issues.jboss.org/browse/ARQ-951
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Reporter: Lukáš Fryč
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> We should know that Drone supports all the listed browsers with all the features like:
> * instantiation
> * destruction
> * reusability
> on following browsers:
> * HtmlUnit
> * Firefox
> * Chrome
> * Internet Explorer
> * Opera
> * Android
> * IPhone
> This will make sure we are able to base our tests on @Drone in QA Lab and verify the high-level functionality like reusability works for all the browsers.
> ----
> The same needs to be addressed in scope of Graphene, see references:
> ARQGRA-59
> support for configurating arquillian.xml during runtime for matrix browser compability jobs
> ARQGRA-76
> Setup matrix jobs for browser support
> ----
> The problem with this approach is that we need to filter what we actually want to test.
> I have identified following types of tetsts in Graphene suite:
> * able to run in any continuous-integration
> ** unit tests
> ** arquillian core integration tests
> ** ftests able to run with htmlunit
> * running only in specific environment
> ** browser-specific
> We need to modify {{arquillian.xml}} in order to select appropriate browser for given run.
> Also, unit-tests shouldn't be run as part of ftests, since it is redundant.
--
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
11 years, 4 months
[JBoss JIRA] (ARQ-951) Drone: Setup Matrix jobs for browser support
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-951?page=com.atlassian.jira.plugin.sy... ]
Karel Piwko updated ARQ-951:
----------------------------
Fix Version/s: (was: drone_1.2.0.next)
> Drone: Setup Matrix jobs for browser support
> --------------------------------------------
>
> Key: ARQ-951
> URL: https://issues.jboss.org/browse/ARQ-951
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Reporter: Lukáš Fryč
>
> We should know that Drone supports all the listed browsers with all the features like:
> * instantiation
> * destruction
> * reusability
> on following browsers:
> * HtmlUnit
> * Firefox
> * Chrome
> * Internet Explorer
> * Opera
> * Android
> * IPhone
> This will make sure we are able to base our tests on @Drone in QA Lab and verify the high-level functionality like reusability works for all the browsers.
> ----
> The same needs to be addressed in scope of Graphene, see references:
> ARQGRA-59
> support for configurating arquillian.xml during runtime for matrix browser compability jobs
> ARQGRA-76
> Setup matrix jobs for browser support
> ----
> The problem with this approach is that we need to filter what we actually want to test.
> I have identified following types of tetsts in Graphene suite:
> * able to run in any continuous-integration
> ** unit tests
> ** arquillian core integration tests
> ** ftests able to run with htmlunit
> * running only in specific environment
> ** browser-specific
> We need to modify {{arquillian.xml}} in order to select appropriate browser for given run.
> Also, unit-tests shouldn't be run as part of ftests, since it is redundant.
--
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
11 years, 4 months
[JBoss JIRA] (ARQGRA-373) Resolving @Location value does not work as expected
by Michael Kotten (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-373?page=com.atlassian.jira.plugin... ]
Michael Kotten updated ARQGRA-373:
----------------------------------
Attachment: ARQGRA-373.patch
Attached a patch that solves the Problem for me.
> Resolving @Location value does not work as expected
> ---------------------------------------------------
>
> Key: ARQGRA-373
> URL: https://issues.jboss.org/browse/ARQGRA-373
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.0.0.Beta1
> Reporter: Michael Kotten
> Attachments: ARQGRA-373.patch
>
>
> The @Location annotation introduced with 2.0.0.Alpha5 does not work as described in the example of http://arquillian.org/blog/2013/09/04/arquillian-graphene-2-0-0-Alpha5/.
> Using a non-absolute location value like "index.html" will throw an exception when trying to browse to the page using Graphene.goTo or using @InitialPage.
> When looking at the sources of LocationEnricher I see 2 problems:
> * contextRootStore is initialized too late in resolve method (line 70). It's already needed during goTo (line 110 in getURLFromLocation) which gets called before initialization (line 68).
> * Using a non-absolute location value leads to an IllegalArgumentException in getURLFromLocation (line 146). I guess the catch block in line 116 is just for this purpose. Unfortunately there will be no URISyntaxException for non-absolute locations. They are perfectly fine URIs (until they get converted to URLs).
>
--
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
11 years, 4 months
[JBoss JIRA] (ARQGRA-373) Resolving @Location value does not work as expected
by Michael Kotten (JIRA)
Michael Kotten created ARQGRA-373:
-------------------------------------
Summary: Resolving @Location value does not work as expected
Key: ARQGRA-373
URL: https://issues.jboss.org/browse/ARQGRA-373
Project: Arquillian Graphene
Issue Type: Bug
Affects Versions: 2.0.0.Beta1
Reporter: Michael Kotten
The @Location annotation introduced with 2.0.0.Alpha5 does not work as described in the example of http://arquillian.org/blog/2013/09/04/arquillian-graphene-2-0-0-Alpha5/.
Using a non-absolute location value like "index.html" will throw an exception when trying to browse to the page using Graphene.goTo or using @InitialPage.
When looking at the sources of LocationEnricher I see 2 problems:
* contextRootStore is initialized too late in resolve method (line 70). It's already needed during goTo (line 110 in getURLFromLocation) which gets called before initialization (line 68).
* Using a non-absolute location value leads to an IllegalArgumentException in getURLFromLocation (line 146). I guess the catch block in line 116 is just for this purpose. Unfortunately there will be no URISyntaxException for non-absolute locations. They are perfectly fine URIs (until they get converted to URLs).
--
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
11 years, 4 months