Difference between revisions of "Requirements for executing in Android"

From GXtest Wiki
Jump to: navigation, search
(Created page with "{{Idiomas|Requerimientos para la ejecución en Android|Requirements for executing in Android| Requirements for executing in Android}} En esta página se listan los requerimie...")
 
(GeneXus configuration)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Idiomas|Requerimientos para la ejecución en Android|Requirements for executing in Android| Requirements for executing in Android}}
+
{{Idiomas|Requerimientos para la ejecución en Android|Requirements for executing in Android| Android での実行要件}}
  
En esta página se listan los requerimientos de software y configuraciones necesarias para poder ejecutar casos de prueba con GXtest sobre un dispositivo o emulador Android.
+
This page enumerates all the software and configuration requirements to be able to test an Android application using GXtest 3.0 (or greater).
  
== Requerimientos del dispositivo móvil ==
+
== Configurations on the Android device ==  
*El sistema operativo instalado en el device o emulador debe ser Android 4.2 o superior.
+
* The device or emulator must have Android 4.2 or greater
*Los emuladores soportados son [http://developer.android.com/tools/help/emulator.html el emulador del SDK de Android] y [http://www.genymotion.com/ GenyMotion].
+
* Suported emulators are [http://developer.android.com/tools/help/emulator.html SDK Android emulator] and [http://www.genymotion.com/ GenyMotion]
  
== Requerimientos de software ==
+
 
 +
== Software requirements ==
 
* Android SDK
 
* Android SDK
Componentes que se instalan desde el SDK Manager:
+
Android SDK Manager components required:
 
* Android SDK Build-tools
 
* Android SDK Build-tools
* Android 4.4.2 API 19 (por defecto las aplicaciones GeneXus se generan para la API 19)
+
* Android 4.4.2 API 19 (by default GeneXus apps are generated for API 19)
 
* Google Play Services
 
* Google Play Services
 
* Google USB Driver
 
* Google USB Driver
Recomendado:
+
Recommended:
* Intel x86 Emulator Accelerator (HAXM installer) - Sólo si se va a ejecutar en un emulador del SDK de Android
+
* Intel x86 Emulator Accelerator (HAXM installer) - Only if you plan to use the SDK Android emulator
 +
 
 +
== GeneXus configuration ==
 +
* The Android application that will be tested must be generated from GeneXus with "Test" mode enabled. This allows to automate the tests on the generated application. To enable this configuration in GeneXus, we must turn on the property "Enable Test Mode":
 +
 
 +
http://wiki.genexus.com/commwiki/servlet/wiki?Android+Enable+Test+Mode+Property,
  
== Configuración en GeneXus ==
+
If we do not have this property available (GeneXus Ev3U2 or U3), we need to edit the ControlTest.java file, which is located inside the GeneXus installation path, in the folder:
* La aplicación Android que se probará debe ser generada en modo "Test" en GeneXus. Esto permite que la aplicación Android generada en GeneXus sea automatizable. Para lograr esto, en GeneXus Ev2 y Ev3U3 es necesario editar el archivo ControlTest.java que se encuentra en la instalación de GeneXus, en el directorio:
+
  
 
Android\FlexibleClient\src\com\artech\ui\test
 
Android\FlexibleClient\src\com\artech\ui\test
  
y descomentar la siguiente línea:
+
Once we find the file, we need to un-comment the following line:
 
control.setContentDescription(definition.getName());
 
control.setContentDescription(definition.getName());
  
Este cambio implica que se incluya información sobre el control en el atributo ContentDesc de Android, para que GXtest pueda identificar los controles. Esto no afecta el comportamiento de la aplicación, y puede ser utilizado para aplicaciones de producción.
+
This change implies that additional information about each control will be included in the ContentDesc attribute of Android controls. This is needed so GXtest can identify each control during test case execution. This setting does not affect the behavior of the generated application, so it can be used as a production version of the app.
  
== Configuración necesaria ==
+
== Other configurations required ==
* Configurar el path al Andorid SDK en GXtest Designer, en el menú Smart Devices -> Settings
+
* You must set the Andorid SDK path in GXtest Designer, by selecting the option menu: Smart Devices -> Configuration.
* Indicar la ruta al apk de la aplicación Android en la variable de proyecto 'apkPath'
+
* After setting the SDK path, by clicking Refresh list, the connected deviced and emulators will be shown. There you may choose the one you want for executing the test case.
* Si va a ejecutar en un dispositivo físico, debe tener los [http://developer.android.com/sdk/win-usb.html drivers compatibles], y configurar el dispositivo siguiendo la [http://developer.android.com/tools/device.html documentación de Android]
+
* Set the path to the application package file (apk file) of the application that will be tested. This path must be set to the project variable named 'apkPath'.
* Para que la ejecución pueda comenzar sin interacción del usuario sobre el dispositivo o emulador, debe quitarse la pantalla de bloqueo de Android. Esto se puede hacer en el dispositivo, en Settings -> Security -> Screen Lock -> None, pero puede variar según el dispositivo y versión de Android.
+
* If you are planning to executing on a real device, you may install the [http://developer.android.com/sdk/win-usb.html USB device compatible drivers], and configure the device following the [http://developer.android.com/tools/device.html Android documentation].
 +
* In order to run the test cases without any interaction with a human, the device shouldn't have any locking settings. To remove the automatic locking settings on the device or emulator, you should enter the device or emulator, and go to Android Settings -> Security -> Screen Lock -> None (this path may change depending on the Android version and device/emulator model).
  
  
Volver a [[GXtest para Smart Devices]]
+
GO back to [[GXtest for Smart Devices]]

Latest revision as of 17:59, 20 November 2015

Spanish.gif
English.gif
Japan.gif

This page enumerates all the software and configuration requirements to be able to test an Android application using GXtest 3.0 (or greater).

Contents

Configurations on the Android device


Software requirements

  • Android SDK

Android SDK Manager components required:

  • Android SDK Build-tools
  • Android 4.4.2 API 19 (by default GeneXus apps are generated for API 19)
  • Google Play Services
  • Google USB Driver

Recommended:

  • Intel x86 Emulator Accelerator (HAXM installer) - Only if you plan to use the SDK Android emulator

GeneXus configuration

  • The Android application that will be tested must be generated from GeneXus with "Test" mode enabled. This allows to automate the tests on the generated application. To enable this configuration in GeneXus, we must turn on the property "Enable Test Mode":

http://wiki.genexus.com/commwiki/servlet/wiki?Android+Enable+Test+Mode+Property,

If we do not have this property available (GeneXus Ev3U2 or U3), we need to edit the ControlTest.java file, which is located inside the GeneXus installation path, in the folder:

Android\FlexibleClient\src\com\artech\ui\test

Once we find the file, we need to un-comment the following line: control.setContentDescription(definition.getName());

This change implies that additional information about each control will be included in the ContentDesc attribute of Android controls. This is needed so GXtest can identify each control during test case execution. This setting does not affect the behavior of the generated application, so it can be used as a production version of the app.

Other configurations required

  • You must set the Andorid SDK path in GXtest Designer, by selecting the option menu: Smart Devices -> Configuration.
  • After setting the SDK path, by clicking Refresh list, the connected deviced and emulators will be shown. There you may choose the one you want for executing the test case.
  • Set the path to the application package file (apk file) of the application that will be tested. This path must be set to the project variable named 'apkPath'.
  • If you are planning to executing on a real device, you may install the USB device compatible drivers, and configure the device following the Android documentation.
  • In order to run the test cases without any interaction with a human, the device shouldn't have any locking settings. To remove the automatic locking settings on the device or emulator, you should enter the device or emulator, and go to Android Settings -> Security -> Screen Lock -> None (this path may change depending on the Android version and device/emulator model).


GO back to GXtest for Smart Devices