Skip to content
This repository has been archived by the owner on Nov 3, 2021. It is now read-only.

Latest commit

 

History

History
329 lines (262 loc) · 11.5 KB

README.md

File metadata and controls

329 lines (262 loc) · 11.5 KB
Raw

Introduction

Gaiatest is a Python package based on Marionette, which is designed specifically for writing tests against Gaia.

Prerequisites

You will need a Marionette enabled Firefox build that you can successfully connect to.

Installation

If you only want to run the tests without developing gaia-ui-tests further:

pip install gaiatest

or

easy_install gaiatest

You can now skip down to the "Risks" section. On the other hand, if you want to modify gaia-ui-tests, do this instead:

git clone https://github.com/mozilla-b2g/gaia.git

The next command will install several python packages on your system such as marionette, gaiatest, and other Mozilla packages. Before you run python setup.py develop, consider setting-up a virtual environment. This is entirely optional.

virtualenv env_name
source env_name/bin/activate

With the virtual environment activated, the python packages will be installed under the env_name folder instead of disturbing your main system.

Finally, do:

cd gaia/tests/python/gaia-ui-tests
python setup.py develop

Risks

Please visit this page to understand and acknowledge the risks involved when running these tests. You have to modify your testvars.json file (see the Test Variables section below,) showing your acknowledgement of the risks, to run the tests.

Command line interface

A helpful command line tool is provided for interacting with Gaia. For full usage details run gcli --help and for help on a specific command use gcli <command> --help.

For example, to unlock the device, set brightness to 100%, connect to an unsecured network, and launch the Settings app:

$ gcli unlock
$ gcli setsetting screen.brightness 1
$ gcli connectwifi MozillaGuest
$ gcli launchapp Settings

Running Tests

To run tests using gaia test, your command-line will vary a little bit depending on what device you're using. The general format is:

gaiatest [options] /path/to/test_foo.py

Options:

--emulator arm --homedir /path/to/emulator:  use these options to
    let Marionette launch an emulator for you in which to run a test
--address <host>:<port>  use this option to run a test on an emulator
    which you've manually launched yourself, a real device, or a b2g
    desktop build.  If you've used port forwarding as described below,
    you'd specify --address localhost:2828
--testvars= (see the Test Variables section below)
--restart restart target instance between tests. This option will remove 
    the /data/local/indexedDB and /data/b2g/mozilla folders and restore the 
    device back to a common state
--yocto gather power draw data while running tests 
    (see https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Platform/Automated_testing/gaia-ui-tests/Gaia_UI_Tests_Run_Tests#Gathering_Power_Draw_Data)
--timeout < time in milliseconds >  to set default timeout values (30s for page load timeout, 
    10s for search timeout and 10s for script timeout) to a common specified value

Testing on a Device

You must run a build of B2G on the device that has Marionette enabled. The easiest way to do that is to grab a nightly eng build, like this one for Unagi (currently it requires a Mozilla LDAP login). Flash that to your device.

You should not enable Remote Debugging manually on the device because there will be competing debuggers. See bug 764913.

If you are running the tests on a device connected via ADB (Android Debug Bridge), you must additionally set up port forwarding from the device to your local machine. You can do this by running the command:

adb forward tcp:2828 tcp:2828

ADB is available in emulator packages under out/host/linux_x86/bin. Alternatively, it may be downloaded as part of the Android SDK.

Testing on Desktop build

You can download the latest build of the desktop client from this location, but make sure you download the appropriate file for your operating system.

  • Linux (32bit): b2g-[VERSION].multi.linux-i686.tar.bz2
  • Linux (64bit): b2g-[VERSION].multi.linux-x86_64.tar.bz2
  • Mac: b2g-[VERSION].multi.mac64.dmg
  • Windows: b2g-[VERSION].multi.win32.zip

Once downloaded, you will need to extract the contents to a local folder. $B2G_HOME refers to the location of the local folder for the remainder of the documentation.

If a profile is specified when running the tests (recommended), a clone of the profile will be used. This helps to ensure that all tests run in a clean state. However, if you also intend to launch and interact with the desktop build manually, we recommend making a copy of the default profile and using the copy for your tests. The location of the default profile is $B2G_HOME/gaia/profile.

To run the tests, use the following command:

gaiatest --restart --type=b2g --app=b2gdesktop \
    --binary=$B2G_HOME/b2g-bin \
    --profile=$B2G_HOME/gaia/profile \
    --testvars=path/to/filename.json \
    gaia/tests/python/gaia-ui-tests/gaiatest/tests/manifest.ini \

You should then start to see the tests running. The next two sections provide details on the test types used in the --type option and the test variables for the --testvars option respectively.

Test Types

Tests can be filtered by type, and the types are defined in the manifest files. Tests can belong to multiple types, some types imply others, and some are mutually exclusive - for example a test cannot be both 'online' and 'offline' but a test that is 'lan' is by definition 'online'. Be warned that despite these rules, there is no error checking on types, so you must take care when assigning them. Default types are set in the [DEFAULT] section of a manifest file, and are inherited by manifest files referenced by an include.

Here is a list of the types used, and when to use them:

  • b2g - this means the test is a B2G (Firefox OS) test. All tests must include this type.
  • antenna - these tests require an antenna (headphones) to be connected.
  • bluetooth - requires bluetooth to be available.
  • camera - these tests require use of a camera.
  • carrier - an active SIM card with carrier connection is required.
  • lan - a local area connection (not cell data) is required by these tests (see note below).
  • offline - specifically requires no online connection.
  • online - some sort of online connection (lan or carrier) is required.
  • qemu - these tests require the Firefox OS emulator to run.
  • sdcard - a storage device must be present.
  • wifi - this means a WiFi connection is required.

You may be thinking that there is only WiFi or cell data, and why the need for the 'lan' test type. Well, these tests aren't only run on mobile devices... We also run then on single-board computers known as pandaboards, which have an ethernet port, and on desktop builds, which share the host computer's connection. It is for this reason that we need 'lan' to indicate a connection that is not cell data. For an example of where online/lan/carrier are used take a look at the browser tests.

Test Variables

We use the --testvars option to pass in local variables, particularly those that cannot be checked into the repository. For example in gaia-ui-tests these variables can be your private login credentials, phone number or details of your WiFi connection.

To use it, copy gaia/tests/python/gaia-ui-tests/gaiatest/testvars_template.json to a different filename but add it into .gitignore so you don't check it into your repository.

When running your tests add the argument: --testvars=(filename).json

Variables:

"carrier": {} (dict) The carrier information of the test phone. This contains the phone number, country and network of the SIM card.

"carrier":{
    "phone_number": "",
    "country": "",
    "network": ""
}

"imei": "" (string) The 12 digit IMEI code of the test phone. "remote_phone_number": "" (string) A phone number that your device can call during the tests (try not to be a nuisance!). Prefix the number with '+' and your international dialing code. "wifi":{}{ (dict) This are the settings of your WiFi connection. Currently this supports WPA/WEP/etc. You can add WiFi networks by doing the following (remember to replace "KeyManagement" and "wep" with the value your network supports) :

"wifi": {
    "ssid": "MyNetwork",
    "keyManagement": "WEP",
    "wep": "MyPassword"
}

WPA-PSK:

"wifi": {
    "ssid": "MyNetwork",
    "keyManagement": "WPA-PSK",
    "psk": "MyPassword"
}

Note: Due to Bug 775499, WiFi connections via WPA-EAP are not capable at this time.

"email": {} (dict) The email login information used by the email tests. It can contain different types of email accounts:

Gmail:

"gmail": {
       "name": "",
       "email": "",
       "password": ""
    }

Or different email protocols:

"IMAP": {
    "name": "",
    "email": "",
    "password": "",
    "imap_hostname": "",
    "imap_name": "",
    "imap_port": "",
    "smtp_hostname": "",
    "smtp_name": "",
    "smtp_port": ""
}

Or:

"ActiveSync":{
    "name": "",
    "email": "",
    "password": "",
    "active_sync_hostname": "",
    "active_sync_username": ""
}

"settings": {} (dict) Custom settings to override the Gaia default settings. These will be set before each test run but are not mandatory.

"settings:{
    "<setting>":<value>
}"

Note: When running with no SIM card or offline the timezone may not be automatically updated to match the local timezone. In that case you may need to force the timezone to match the desired timezone using settings in testvars.json which will set it during the test setUp:

"settings:{
    "time.timezone": <value>,
    "time.timezone.user-selected": <value>
}"

Don't forget to acknowledged risks in your testvars file after you have visited the Risks page to understand and acknowledge the risks involved when running these tests, or the tests will not be run.

Test data Prerequisites

Occasionally a test will need data on the hardware that cannot be set during the test setUp. The following tests need data set up before they can be run successfully:

test_ftu Requires a single record/contact saved onto the SIM card to test the SIM contact import

Writing Tests

Test writing for Marionette Python tests is described at https://developer.mozilla.org/en-US/docs/Marionette/Marionette_Python_Tests.

Additionally, gaiatest exposes some API's for managing Gaia's lockscreen and application manager. See https://github.com/mozilla-b2g/gaia/blob/master/tests/python/gaiatest/gaia_test.py.

At the moment we don't have a specific style guide. Please follow the prevailing style of the existing tests. Use them as a template for writing your tests. We follow PEP8 for formatting, although we're pretty lenient on the 80-character line length.