October 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-392) Update and enhance Graphene guide

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-392?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-392: ----------------------------------- Hey Juraj, I agree that we should address this as soon as possible, but we don't have to postpone Final because of it. Feel free to submit the suggested changes once you identify where to put them. > Update and enhance Graphene guide > --------------------------------- > > Key: ARQGRA-392 > URL: https://issues.jboss.org/browse/ARQGRA-392 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: doc > Affects Versions: 2.0.0.CR2 > Reporter: Juraj Húska > Priority: Minor > Fix For: 2.0-Tracking > > > The Graphene guide at arquillian.org deserves couple of enhancements and updates: > *enhancements*: > * make the reference to the reference documentation more explicit - put it under own header, so it appears in the right menu > * consider referencing a link how to use jboss boms, or boms in general > *updates* > * update the versions of the artifacts once the Final is out > I would suggest to incorporate this improvements after Graphene 2.0.0.Final is released. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-392) Update and enhance Graphene guide

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-392?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-392: ------------------------------ Fix Version/s: 2.0-Tracking > Update and enhance Graphene guide > --------------------------------- > > Key: ARQGRA-392 > URL: https://issues.jboss.org/browse/ARQGRA-392 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: doc > Affects Versions: 2.0.0.CR2 > Reporter: Juraj Húska > Priority: Minor > Fix For: 2.0-Tracking > > > The Graphene guide at arquillian.org deserves couple of enhancements and updates: > *enhancements*: > * make the reference to the reference documentation more explicit - put it under own header, so it appears in the right menu > * consider referencing a link how to use jboss boms, or boms in general > *updates* > * update the versions of the artifacts once the Final is out > I would suggest to incorporate this improvements after Graphene 2.0.0.Final is released. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1526) Provide screenshot api for Droidium container

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1526?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1526. ------------------------------------ Fix Version/s: droidium_1.0.0.Alpha2 Resolution: Done > Provide screenshot api for Droidium container > --------------------------------------------- > > Key: ARQ-1526 > URL: https://issues.jboss.org/browse/ARQ-1526 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha2 > > > Screenshot API depends on ddmlib artifact in arquillian-droidium-container-api. Get rid of this dependency by providing screenshot API so only implementation depends on it. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1525) Be able to deploy APKs when doing web testing with web plugin

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1525?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1525. ------------------------------------ Fix Version/s: droidium_1.0.0.Alpha2 Resolution: Done > Be able to deploy APKs when doing web testing with web plugin > ------------------------------------------------------------- > > Key: ARQ-1525 > URL: https://issues.jboss.org/browse/ARQ-1525 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha2 > > > Now, user can not deploy packages to Android device when he uses web plugin. Even the usage and profit of having Android packages installed on device when doing web testing against application container is quite questionable, it is needed anyway. There is not any reason why user should not be able to install packages as normal deployments to Android device even he is focused on web testing mainly. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1524) Implement deployment logic when native plugin is not on class path

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1524?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1524. ------------------------------------ Fix Version/s: droidium_1.0.0.Alpha2 Resolution: Done > Implement deployment logic when native plugin is not on class path > ------------------------------------------------------------------ > > Key: ARQ-1524 > URL: https://issues.jboss.org/browse/ARQ-1524 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha2 > > > When native plugin is not on class path, we can install packages to Android device directly via Android's injection install and uninstall methods however since Android container without native plugin is not capable to follow Arquillian deployment logic, we have to use these methods so @Deployment method has to be kind of dummy. > There has to be deployment logic implemented when native plugin is not on class path. This has to be investigated further. > This is the logical continuation of ARQ-1521 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1526) Provide screenshot api for Droidium container

by Stefan Miklosovic (JIRA)

Stefan Miklosovic created ARQ-1526: -------------------------------------- Summary: Provide screenshot api for Droidium container Key: ARQ-1526 URL: https://issues.jboss.org/browse/ARQ-1526 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha1 Reporter: Stefan Miklosovic Screenshot API depends on ddmlib artifact in arquillian-droidium-container-api. Get rid of this dependency by providing screenshot API so only implementation depends on it. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1525) Be able to deploy APKs when doing web testing with web plugin

by Stefan Miklosovic (JIRA)

Stefan Miklosovic created ARQ-1525: -------------------------------------- Summary: Be able to deploy APKs when doing web testing with web plugin Key: ARQ-1525 URL: https://issues.jboss.org/browse/ARQ-1525 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha1 Reporter: Stefan Miklosovic Now, user can not deploy packages to Android device when he uses web plugin. Even the usage and profit of having Android packages installed on device when doing web testing against application container is quite questionable, it is needed anyway. There is not any reason why user should not be able to install packages as normal deployments to Android device even he is focused on web testing mainly. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1507) Make usage of Arquillian Droidium stack easier

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1507?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1507. ------------------------------------ Resolution: Done > Make usage of Arquillian Droidium stack easier > ---------------------------------------------- > > Key: ARQ-1507 > URL: https://issues.jboss.org/browse/ARQ-1507 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha2 > > > Currently, Droidium consists of 3 thinks: > 1/ Container > 2/ Native extension > 3/ Web extension > User can arbitrary combine these extensions. For that reason, it would be great if container, which is always used, will emit some huge warning in case that it discovers Drone is injected and browser==android and web extension is missing on class path. Similarly, container should be able to figure out that native extension is missing but it will likely be needed - as it has access to @Instrumented deployments. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1507) Make usage of Arquillian Droidium stack easier

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1507?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1507: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha2 > Make usage of Arquillian Droidium stack easier > ---------------------------------------------- > > Key: ARQ-1507 > URL: https://issues.jboss.org/browse/ARQ-1507 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha2 > > > Currently, Droidium consists of 3 thinks: > 1/ Container > 2/ Native extension > 3/ Web extension > User can arbitrary combine these extensions. For that reason, it would be great if container, which is always used, will emit some huge warning in case that it discovers Drone is injected and browser==android and web extension is missing on class path. Similarly, container should be able to figure out that native extension is missing but it will likely be needed - as it has access to @Instrumented deployments. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1507) Make usage of Arquillian Droidium stack easier

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1507?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic commented on ARQ-1507: ---------------------------------------- https://github.com/arquillian/arquillian-droidium/commit/84b0bfe2eaddeef4... Warning is printed out only when there is an extension which qualifier starts with "webdriver" and browser name (browser or browserName) is present and has value of "android". > Make usage of Arquillian Droidium stack easier > ---------------------------------------------- > > Key: ARQ-1507 > URL: https://issues.jboss.org/browse/ARQ-1507 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > Currently, Droidium consists of 3 thinks: > 1/ Container > 2/ Native extension > 3/ Web extension > User can arbitrary combine these extensions. For that reason, it would be great if container, which is always used, will emit some huge warning in case that it discovers Drone is injected and browser==android and web extension is missing on class path. Similarly, container should be able to figure out that native extension is missing but it will likely be needed - as it has access to @Instrumented deployments. -- 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, 6 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 October 2013