1146909 - Develop Gaia Acceptance: Establish Gaia Acceptance backlog with existing Python UI tests to port

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::UI Tests, defect)

Description

[Johan Lorenzo [:jlorenzo]]

From https://wiki.mozilla.org/B2G/QA/Automation/UI/Strategy/Port_Gaia_Integration_Python

Comment 1

[Johan Lorenzo [:jlorenzo]]

Attachment: Backlog spreadsheet

I created a new spreadsheet in the same way as the one for CI tests. I roughly estimated the priority by the following:
* Each test which is run in the smoketest suite is either a 1 or a 2
* The other are a 3 or a 4.
* The ones with 99 are the ones I think they don't belong to the acceptance suite. 

The details of the scale is in the spreadsheet. 

The prioritized list is in a separate sheet (and gets its data from the "raw data sheet").

It'll probably need to be adjusted, especially if we want to explicitly mention the user stories.

The first iteration should be done by now. Feel free to reopen if you think some major work needs to be executed for this first version.

Comment 2

[Martijn Wargers (dead)]

This is the spreadsheet: https://docs.google.com/a/mozilla.com/spreadsheets/d/19ArBw8JpklhCkGn_YpiYbJGD1jstujegtljjF0brf4I

Comment 3

[Martijn Wargers (dead)]

Some other limitations of MarionetteJS (apart from the fact that it doesn't run on device yet):
https://wiki.mozilla.org/B2G/QA/Automation/UI/MarionetteJS_On_Device_Status#Limitations_of_MarionetteJS
    Not possible to run from a manifest
        So things like filter by abilities (like "is a SIM card required?") is not possible
    Not possible to push/pull/delete files on the device
    Not possible to run on a 319MB device
        Currently, MarionetteJS requires more memory than gaia-ui test

So we should beware of that and first pick tests that are not hindered by those limitations of MarionetteJS.