Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
colourGreen
titleupdate 25 nov 2024

Info

In this section, you will find how to launch a functional journey analysis on a local android device as it has been described in the Getting started part.

...

  • If possible, set the language to 'English - United Kingdom

Validate access to your application

On your local smartphone, check that you can use your application correctly: the mobile application reaches all your servers, and your web application accesses all your web services, which are necessary for it to work properly.

...

  • United Kingdom

...

[Optional] Create an application on the Greenspector App

If it is not done and you want to save measures on the web interface, create an application on Greenspector AppStudio

  • Go to the Applications menu

  • Click on Add an application Enter a name, a first version and description (not obligatory)New Analysis

  • Enter needed information

  • Validate

Complete files

Info

To launch tests, the testrunner executable needs config and job files. For more information about the content of these files, check the section Complementary files (Android) .

...

  • ${PHONE_IP} by your phone's IP address

  • ${PHONE_PORT} by 5555

  • ${PATH_TO_ADB} by the path to the adb executable. Simply write "adb" if this command is already in your environment variables.

  • ${PATH_TO_AAPT} by the path of the aapt executable. Simply write "aapt" if this command is already in your environment variables.

  • ${GREENSPECTOR_CORE_SERVER_URL} by https://appcore-saas-prod.greenspector.com

  • ${PRIVATE_TOKEN} by your token. To find your token, go to the Greenspector interface, click on your name in the top right-hand corner, then click on the "Preferences" tab.

...

...

Tip

If the test succeeds, you can continue to write your script by following best practices (smile)

If your script is finished and ready to launch official measurements, follow:

Warning

If the test doesn’t succeed, you can consult the downloadable error report files :

  • A problematic line in the test file : This may indicate that the element you are trying to click on or waiting for is not accessible or present.

  • The failed.png image with a screenshot of the last screen before the error. This allows you to quickly identify the malfunction.

  • Screenshots of the steps that worked before the failed.

  • The dump.uix file, which contains an extraction of the screen composition. You can search this file for the text you want to automate, as well as the identifier of that element.

If the text is present in the failed screen and dump.uix but you get an error, it's possible that the element is not technically accessible. You can search for the element’s id in dump.uix and use an automation keyword such as clickById or waitById.

Refer to Methods details and appropriate troubleshooting according your displayed error.

Expand
titleRecurring errors

...

If you registered measures are stored online on https://app.greenspector.com/app/list Greenspector Studio by online=true in job.yml, versions, versions are visible in the Meter tab.

...