Difference between revisions of "Requirements for executing in Android"
From GXtest Wiki
(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...") |
|||
| 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| Requirements for executing in Android}} | ||
| − | + | This page enumerates all the software and configuration requirements to be able to test an Android application using GXtest. | |
| − | == | + | == Configurations on the Android device == |
| − | * | + | * The device or emulator must have Android 4.2 or greater |
| − | * | + | * Suported emulators are [http://developer.android.com/tools/help/emulator.html SDK Android emulator] and [http://www.genymotion.com/ GenyMotion] |
| − | == | + | |
| + | == Software requirements == | ||
* Android SDK | * Android SDK | ||
| − | + | Android SDK Manager components required: | |
* Android SDK Build-tools | * Android SDK Build-tools | ||
| − | * Android 4.4.2 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 | ||
| − | + | Recommended: | |
| − | * Intel x86 Emulator Accelerator (HAXM installer) - | + | * 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 Ev2 and Ev3U3, we must edit the ControlTest.java file, which is located inside the GeneXus installation path, in the folder: |
Android\FlexibleClient\src\com\artech\ui\test | Android\FlexibleClient\src\com\artech\ui\test | ||
| − | + | Once we find the file, we need to un-comment the following line: | |
control.setContentDescription(definition.getName()); | 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. | |
== Configuración necesaria == | == Configuración necesaria == | ||
Revision as of 16:41, 16 April 2015
 |
 |
 |
This page enumerates all the software and configuration requirements to be able to test an Android application using GXtest.
Contents |
Configurations on the Android device
- The device or emulator must have Android 4.2 or greater
- Suported emulators are SDK Android emulator and GenyMotion
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 Ev2 and Ev3U3, we must 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.
Configuración necesaria
- Configurar el path al Andorid SDK en GXtest Designer, en el menú Smart Devices -> Settings
- Indicar la ruta al apk de la aplicación Android en la variable de proyecto 'apkPath'
- Si va a ejecutar en un dispositivo físico, debe tener los drivers compatibles, y configurar el dispositivo siguiendo la documentación de Android
- 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.
Volver a GXtest para Smart Devices
