[JBoss JIRA] (ARQ-1522) Should be able to start activity without FQDN format
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1522?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reassigned ARQ-1522:
--------------------------------------
Assignee: Stefan Miklosovic
> Should be able to start activity without FQDN format
> ----------------------------------------------------
>
> Key: ARQ-1522
> URL: https://issues.jboss.org/browse/ARQ-1522
> 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
> Assignee: Stefan Miklosovic
> Priority: Minor
>
> Given:
> I have activities which can be started via activity manager.
> When:
> I want to start some activity
> Expect:
> It is sufficient to use its simple name instead of FQDN.
> Example:
> {code}android.getActivityManagerProvider().getActivityManager().startActivity("io.selendroid.testapp.HomeScreenActivity");{code}
> should equal to
> {code}android.getActivityManagerProvider().getActivityManager().startActivity("HomeScreenActivity");{code}
> In case there are two activities with same simple name, exception has to be thrown.
--
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
[JBoss JIRA] (ARQ-1522) Should be able to start activity without FQDN format
by Stefan Miklosovic (JIRA)
Stefan Miklosovic created ARQ-1522:
--------------------------------------
Summary: Should be able to start activity without FQDN format
Key: ARQ-1522
URL: https://issues.jboss.org/browse/ARQ-1522
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
Priority: Minor
Given:
I have activities which can be started via activity manager.
When:
I want to start some activity
Expect:
It is sufficient to use its simple name instead of FQDN.
Example:
{code}android.getActivityManagerProvider().getActivityManager().startActivity("io.selendroid.testapp.HomeScreenActivity");{code}
should equal to
{code}android.getActivityManagerProvider().getActivityManager().startActivity("HomeScreenActivity");{code}
In case there are two activities with same simple name, exception has to be thrown.
--
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
[JBoss JIRA] (ARQ-1521) Implement default activity manager when native plugin is not on the class path
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1521?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1521:
-----------------------------------
Description:
Once user puts native plugin on class path, he can manage activities via NativeActivityManager however when he does no put this plugin on the class path, after he injects AndroidDevice, he is not able to start activities because ActivityManager implementation is null.
In order to be able to start activities even when native plugin is missing, there has to be default ActivityManager implementation which does not uses WebDriver or Selendroid but it executes shell commands instead of that.
However, even after implementing this, it is questionable for what reason a user would start the activity when he can not control it by any means since WebDriver is missing and we can not inject it via Drone as well.
was:
Once user puts native plugin on class path, he can manage activities via NativeActivityManager however when he does no put this plugin on the class path, after he injects AndroidDevice, he is not able to start activities because ActivityManager implementation is null.
In order to be able to start activities even when native plugin is missing, there has to be default ActivityManager implementation which does not uses WebDriver or Selendroid but it executes shell commands instead of that.
> Implement default activity manager when native plugin is not on the class path
> ------------------------------------------------------------------------------
>
> Key: ARQ-1521
> URL: https://issues.jboss.org/browse/ARQ-1521
> 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
>
> Once user puts native plugin on class path, he can manage activities via NativeActivityManager however when he does no put this plugin on the class path, after he injects AndroidDevice, he is not able to start activities because ActivityManager implementation is null.
> In order to be able to start activities even when native plugin is missing, there has to be default ActivityManager implementation which does not uses WebDriver or Selendroid but it executes shell commands instead of that.
> However, even after implementing this, it is questionable for what reason a user would start the activity when he can not control it by any means since WebDriver is missing and we can not inject it via Drone as well.
--
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
[JBoss JIRA] (ARQ-1521) Implement default activity manager when native plugin is not on the class path
by Stefan Miklosovic (JIRA)
Stefan Miklosovic created ARQ-1521:
--------------------------------------
Summary: Implement default activity manager when native plugin is not on the class path
Key: ARQ-1521
URL: https://issues.jboss.org/browse/ARQ-1521
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
Once user puts native plugin on class path, he can manage activities via NativeActivityManager however when he does no put this plugin on the class path, after he injects AndroidDevice, he is not able to start activities because ActivityManager implementation is null.
In order to be able to start activities even when native plugin is missing, there has to be default ActivityManager implementation which does not uses WebDriver or Selendroid but it executes shell commands instead of that.
--
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
[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 reassigned ARQ-1507:
--------------------------------------
Assignee: Stefan Miklosovic
> 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
[JBoss JIRA] (ARQ-1505) Wrong handling of Android Debug Bridge initialization
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1505?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1505:
-----------------------------------
Fix Version/s: droidium_1.0.0.Alpha2
> Wrong handling of Android Debug Bridge initialization
> -----------------------------------------------------
>
> Key: ARQ-1505
> URL: https://issues.jboss.org/browse/ARQ-1505
> Project: Arquillian
> Issue Type: Bug
> 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
>
>
> When ADB is started, but the port is already occupied by a different tooling, it logs an E/ddms message, however it continues with the execution.
> This is indeed faulty behaviour. The port should be configurable, if the port is occupied - it should fail with Unable to start container or unable to connect to the running container exception - similar to behavior you experience with other remote / managed containers.
> {code}
> org.arquillian.droidium.container.impl.AndroidBridgeImpl connect
> INFO: Connecting to the Android Debug Bridge at /home/kpiwko/apps/android-sdk-linux_x86/platform-tools/adb forceNewBridge = true
> 10:01:23 E/ddms: Could not open Selected VM debug port (8700). Make sure you do not have another instance of DDMS or of the eclipse plugin running. If it's being used by
> something else, choose a new port number in the preferences.
> Sep 27, 2013 10:01:23 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge
> INFO: Android Debug Bridge was initialized in 350ms.
> {code}
--
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
[JBoss JIRA] (ARQ-1505) Wrong handling of Android Debug Bridge initialization
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1505?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reassigned ARQ-1505:
--------------------------------------
Assignee: Stefan Miklosovic
> Wrong handling of Android Debug Bridge initialization
> -----------------------------------------------------
>
> Key: ARQ-1505
> URL: https://issues.jboss.org/browse/ARQ-1505
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
>
> When ADB is started, but the port is already occupied by a different tooling, it logs an E/ddms message, however it continues with the execution.
> This is indeed faulty behaviour. The port should be configurable, if the port is occupied - it should fail with Unable to start container or unable to connect to the running container exception - similar to behavior you experience with other remote / managed containers.
> {code}
> org.arquillian.droidium.container.impl.AndroidBridgeImpl connect
> INFO: Connecting to the Android Debug Bridge at /home/kpiwko/apps/android-sdk-linux_x86/platform-tools/adb forceNewBridge = true
> 10:01:23 E/ddms: Could not open Selected VM debug port (8700). Make sure you do not have another instance of DDMS or of the eclipse plugin running. If it's being used by
> something else, choose a new port number in the preferences.
> Sep 27, 2013 10:01:23 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge
> INFO: Android Debug Bridge was initialized in 350ms.
> {code}
--
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
[JBoss JIRA] (ARQ-1505) Wrong handling of Android Debug Bridge initialization
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1505?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1505.
------------------------------------
Resolution: Done
> Wrong handling of Android Debug Bridge initialization
> -----------------------------------------------------
>
> Key: ARQ-1505
> URL: https://issues.jboss.org/browse/ARQ-1505
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
>
> When ADB is started, but the port is already occupied by a different tooling, it logs an E/ddms message, however it continues with the execution.
> This is indeed faulty behaviour. The port should be configurable, if the port is occupied - it should fail with Unable to start container or unable to connect to the running container exception - similar to behavior you experience with other remote / managed containers.
> {code}
> org.arquillian.droidium.container.impl.AndroidBridgeImpl connect
> INFO: Connecting to the Android Debug Bridge at /home/kpiwko/apps/android-sdk-linux_x86/platform-tools/adb forceNewBridge = true
> 10:01:23 E/ddms: Could not open Selected VM debug port (8700). Make sure you do not have another instance of DDMS or of the eclipse plugin running. If it's being used by
> something else, choose a new port number in the preferences.
> Sep 27, 2013 10:01:23 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge
> INFO: Android Debug Bridge was initialized in 350ms.
> {code}
--
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
[JBoss JIRA] (ARQ-1513) Multicontainer extension should not log warnings about its property
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1513?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic commented on ARQ-1513:
----------------------------------------
The idea discussed with Karel is that in order to get rid of that warning message, you just can not use that property what in turn means we should "guess" that some particular container definition is related to some container adapter located on the class path. E.g. when qualifier contains jboss or there is some specific property used in container definition, it is very high chance that this container def will be related to container adapter class on the classpath of some jboss as adapter. This approach can be done with Android container as well.
One disadvantage of this approach is that we would have to cover all container adapters a we would try to match them but I humbly guess having covered the recognition of just jbosses, glassfishes and android adapters is pretty much ok for almost any user.
This warning gets printed only in the case there are more then one container adapter on classpath since we have to make difference between them. When you are using only one container adapter (like Android), you do not have to add adapterImplClass since there is exact matching between container definition and class on classpath implementing DeployableContainer.
> Multicontainer extension should not log warnings about its property
> -------------------------------------------------------------------
>
> Key: ARQ-1513
> URL: https://issues.jboss.org/browse/ARQ-1513
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Priority: Minor
>
> All the time, following WARNING is present in the log:
> {code}
> Unused property entries: {adapterImplClass=org.arquillian.droidium.container.AndroidDeployableContainer}
> {code}
> As this property is required, the warning should be somehow suppressed.
--
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
[JBoss JIRA] (ARQ-1495) Support both serialId and avdName in arquillian.xml
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1495?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1495.
------------------------------------
Resolution: Done
> Support both serialId and avdName in arquillian.xml
> ---------------------------------------------------
>
> Key: ARQ-1495
> URL: https://issues.jboss.org/browse/ARQ-1495
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: droidium_1.0.0.Alpha2
>
>
> When serialId and avdName are both in arquillian.xml container configuration, try to firstly connect to physical device (according to serialId), when this fails, try to connect to avdName.
> Right now when serialId is used in connection with avdName and there is a failure to connect to physical device via serialId, the execution is aborted.
> This is not very comfortable from test execution point of view.
--
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