September 2013 - arquillian-issues

[JBoss JIRA] (ARQGRA-372) Make Graphene compatible with Drone 1.2.0.Beta2 SPI

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-372: --------------------------------- Summary: Make Graphene compatible with Drone 1.2.0.Beta2 SPI Key: ARQGRA-372 URL: https://issues.jboss.org/browse/ARQGRA-372 Project: Arquillian Graphene Issue Type: Component Upgrade Reporter: Lukáš Fryč -- 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-437) Introduce annotation to control lifecycle of selenium session

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-437?page=com.atlassian.jira.plugin.sy... ] Lukáš Fryč commented on ARQ-437: -------------------------------- +1 > Introduce annotation to control lifecycle of selenium session > ------------------------------------------------------------- > > Key: ARQ-437 > URL: https://issues.jboss.org/browse/ARQ-437 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Lukáš Fryč > > Following options are being considered: > BEFORE_SUITE > BEFORE_CLASS > BEFORE_METHOD -- 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č updated ARQ-1385: ---------------------------- Description: 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... was: 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... > 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1477) Recognize more file extensions as valid for deployment methods

by Stefan Miklosovic (JIRA)

Stefan Miklosovic created ARQ-1477: -------------------------------------- Summary: Recognize more file extensions as valid for deployment methods Key: ARQ-1477 URL: https://issues.jboss.org/browse/ARQ-1477 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Stefan Miklosovic Priority: Optional Since there are some Android-Arquillian testing experiments where I deploy APK to Android device (emulator) directly from deployment method (APK is a JavaArchive anyway), I am seeing this warning message in the output: Sep 11, 2013 5:05:09 PM org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator logWarningIfArchiveHasUnexpectedFileExtension WARNING: Deployment archive of type JavaArchiveImpl has been given an unexpected file extension. Archive name: some-android-app.apk, deployment name: android. It might not be wrong, but the container will rely on the given file extension, the archive type is only a description of a certain structure. I know that the proper way to do this is to implement AndroidArchive into ShrinkWrap and add it into container.spi.client.deployment.Validate but that is very long run and I am looking for another way or at least to report this that it is an issue for the next generation ... -- 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-437) Introduce annotation to control lifecycle of selenium session

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-437?page=com.atlassian.jira.plugin.sy... ] Karel Piwko commented on ARQ-437: --------------------------------- Thinking about this, it should be possible to indirect entrance events by Drone's own event. Than is: Drone @Observes BeforeClass and fires PrepareDroneConfigurationEvent(). Another observer will @Observe this event and react on that. In such case, it should be possible to provide a global Drone configuration to ignore @BeforeClass event altogether and let user write his own extension to fire PrepareDroneConfigurationEvent manually. This might be interesting especially for Suite based runners. > Introduce annotation to control lifecycle of selenium session > ------------------------------------------------------------- > > Key: ARQ-437 > URL: https://issues.jboss.org/browse/ARQ-437 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Lukáš Fryč > > Following options are being considered: > BEFORE_SUITE > BEFORE_CLASS > BEFORE_METHOD -- 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-1476) Improve Drone Test Enricher loggging

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1476?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1476. ------------------------------ Assignee: Karel Piwko Fix Version/s: drone_1.2.0.Beta2 Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/acdbf81d2... > Improve Drone Test Enricher loggging > ------------------------------------ > > Key: ARQ-1476 > URL: https://issues.jboss.org/browse/ARQ-1476 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Beta1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.2.0.Beta2 > > > Log all the information required in order to identify field/parameter in case that FINE logging is enabled. -- 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-1476) Improve Drone Test Enricher loggging

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1476?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1476: ----------------------------- Affects Version/s: drone_1.2.0.Beta1 > Improve Drone Test Enricher loggging > ------------------------------------ > > Key: ARQ-1476 > URL: https://issues.jboss.org/browse/ARQ-1476 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: drone_1.2.0.Beta1 > Reporter: Karel Piwko > Priority: Minor > > Log all the information required in order to identify field/parameter in case that FINE logging is enabled. -- 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-1476) Improve Drone Test Enricher loggging

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1476?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1476: ----------------------------- Component/s: Extension - Drone > Improve Drone Test Enricher loggging > ------------------------------------ > > Key: ARQ-1476 > URL: https://issues.jboss.org/browse/ARQ-1476 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Beta1 > Reporter: Karel Piwko > Priority: Minor > > Log all the information required in order to identify field/parameter in case that FINE logging is enabled. -- 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-1476) Improve Drone Test Enricher loggging

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1476: -------------------------------- Summary: Improve Drone Test Enricher loggging Key: ARQ-1476 URL: https://issues.jboss.org/browse/ARQ-1476 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Karel Piwko Priority: Minor Log all the information required in order to identify field/parameter in case that FINE logging is enabled. -- 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-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 resolved ARQ-1475. ------------------------------ Assignee: Karel Piwko Fix Version/s: drone_1.2.0.Beta2 Resolution: Done Fixed by providing a new SPI class *DroneInstanceEnhancer* and marking previous implementation as deprecated, while still compatible. Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/d5f47c5f5... > 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

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