November 2013 - arquillian-issues

[JBoss JIRA] (ARQ-1583) Emulator does not figure out process had died

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1583?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1583: ----------------------------- Priority: Critical (was: Major) > Emulator does not figure out process had died > --------------------------------------------- > > Key: ARQ-1583 > URL: https://issues.jboss.org/browse/ARQ-1583 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Priority: Critical > > *When*: > I let Droidium start emulator. > *Given*: > DISPLAY is not set. > *Then*: > Droidium waits up to emulator start time, then fails. > *Expected*: > Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1583) Emulator does not figure out process had died

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1583?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1583: ---------------------------------- Updated issue and bumped priority. The problem is that Droidium will not figure out emulator process is down and still waits for it's output. > Emulator does not figure out process had died > --------------------------------------------- > > Key: ARQ-1583 > URL: https://issues.jboss.org/browse/ARQ-1583 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Priority: Critical > > *When*: > I let Droidium start emulator. > *Given*: > Emulator command fails, for instance when DISPLAY is not set. > *Then*: > Droidium waits up to emulator start time, then fails. > *Expected*: > Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1583) Emulator does not figure out that DISPLAY is not available

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1583?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1583: ----------------------------- Description: *When*: I let Droidium start emulator. *Given*: DISPLAY is not set. *Then*: Droidium waits up to emulator start time, then fails. *Expected*: Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. was: *When*: I let Droidium start emulator. *Given*: DISPLAY is not set. *Then*: Droidium waits up to emulator start time. *Expected*: Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. > Emulator does not figure out that DISPLAY is not available > ---------------------------------------------------------- > > Key: ARQ-1583 > URL: https://issues.jboss.org/browse/ARQ-1583 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > > *When*: > I let Droidium start emulator. > *Given*: > DISPLAY is not set. > *Then*: > Droidium waits up to emulator start time, then fails. > *Expected*: > Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1583) Emulator does not figure out that DISPLAY is not available

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1583: -------------------------------- Summary: Emulator does not figure out that DISPLAY is not available Key: ARQ-1583 URL: https://issues.jboss.org/browse/ARQ-1583 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha2 Reporter: Karel Piwko *When*: I let Droidium start emulator. *Given*: DISPLAY is not set. *Then*: Droidium waits up to emulator start time. *Expected*: Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1582) Honor ANDROID_SDK_HOME, deprecate generatedAvdPath

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1582?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1582: ---------------------------------- One more note, keystore and androidDebugKey should be read from ANDROID_SDK_HOME as well. > Honor ANDROID_SDK_HOME, deprecate generatedAvdPath > -------------------------------------------------- > > Key: ARQ-1582 > URL: https://issues.jboss.org/browse/ARQ-1582 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > > ANDROID_SDK_HOME represents a top level directory that is used to store metadata of AVDs. By default, this directory equals $HOME. > However, various plugins and tools - such as Jenkins Android Plugin, allow to change ANDROID_SDK_HOME to better isolate jobs. > Droidium should be able to: > * pass androidSdkHome in arquillian.xml with default = user.home > * honor this directoryand create generated AVDs there - this will limit write access to single location - e.g. pattern would be ${androidSdkHome}/.android/${avdName}.avd > Then, *generatedAvdPath* can be dropped altogether - reasoning is that Android UI does not allow that neither and it does not make much sense to split metadata and AVD itself. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1582) Honor ANDROID_SDK_HOME, deprecate generatedAvdPath

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1582?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic reassigned ARQ-1582: -------------------------------------- Assignee: Stefan Miklosovic > Honor ANDROID_SDK_HOME, deprecate generatedAvdPath > -------------------------------------------------- > > Key: ARQ-1582 > URL: https://issues.jboss.org/browse/ARQ-1582 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > ANDROID_SDK_HOME represents a top level directory that is used to store metadata of AVDs. By default, this directory equals $HOME. > However, various plugins and tools - such as Jenkins Android Plugin, allow to change ANDROID_SDK_HOME to better isolate jobs. > Droidium should be able to: > * pass androidSdkHome in arquillian.xml with default = user.home > * honor this directoryand create generated AVDs there - this will limit write access to single location - e.g. pattern would be ${androidSdkHome}/.android/${avdName}.avd > Then, *generatedAvdPath* can be dropped altogether - reasoning is that Android UI does not allow that neither and it does not make much sense to split metadata and AVD itself. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1582) Honor ANDROID_SDK_HOME, deprecate generatedAvdPath

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1582: -------------------------------- Summary: Honor ANDROID_SDK_HOME, deprecate generatedAvdPath Key: ARQ-1582 URL: https://issues.jboss.org/browse/ARQ-1582 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha2 Reporter: Karel Piwko ANDROID_SDK_HOME represents a top level directory that is used to store metadata of AVDs. By default, this directory equals $HOME. However, various plugins and tools - such as Jenkins Android Plugin, allow to change ANDROID_SDK_HOME to better isolate jobs. Droidium should be able to: * pass androidSdkHome in arquillian.xml with default = user.home * honor this directoryand create generated AVDs there - this will limit write access to single location - e.g. pattern would be ${androidSdkHome}/.android/${avdName}.avd Then, *generatedAvdPath* can be dropped altogether - reasoning is that Android UI does not allow that neither and it does not make much sense to split metadata and AVD itself. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-155) Run QUnit tests using Maven plugin or Arquillian JavaScript extension

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-155?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-155: ----------------------------------- [~okiss], could you please share the code what you have so we can take a look? Let's open a branch on your fork of Graphene, please. > Run QUnit tests using Maven plugin or Arquillian JavaScript extension > --------------------------------------------------------------------- > > Key: ARQGRA-155 > URL: https://issues.jboss.org/browse/ARQGRA-155 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Oliver Kišš > Priority: Optional > Labels: padawan > Fix For: 2.0-Tracking > > > http://code.google.com/p/qunit-maven-plugin/ -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-414) Update some ftests to pass with Safari

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-414?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-414: ------------------------------ Summary: Update some ftests to pass with Safari (was: Update ftest to pass with Safari) > Update some ftests to pass with Safari > -------------------------------------- > > Key: ARQGRA-414 > URL: https://issues.jboss.org/browse/ARQGRA-414 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: ftest > Affects Versions: 2.0.0.Final > Reporter: Jiri Locker > > Support for SafariDriver was recently added to Drone. It is possible to run ftest agaist Safari (on Mac) with {{mvn clean test -Dbrowser=safari}} in ftest module. > The initial result was 16 failures out of 274 tests. The failing tests should be fixed before stating Safari support by Graphene. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-414) Update some ftests to pass with Safari

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-414?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-414: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 2.0.1.Final Resolution: Done > Update some ftests to pass with Safari > -------------------------------------- > > Key: ARQGRA-414 > URL: https://issues.jboss.org/browse/ARQGRA-414 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: ftest > Affects Versions: 2.0.0.Final > Reporter: Jiri Locker > Fix For: 2.0.1.Final > > > Support for SafariDriver was recently added to Drone. It is possible to run ftest agaist Safari (on Mac) with {{mvn clean test -Dbrowser=safari}} in ftest module. > The initial result was 16 failures out of 274 tests. The failing tests should be fixed before stating Safari support by Graphene. -- 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, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues November 2013