B2G/QA/Automation/UI/Strategy/Criteria Gaia Acceptance Tests: Difference between revisions
< B2G | QA | Automation | UI | Strategy
Jump to navigation
Jump to search
(Created page with "=Objective= For developing Gaia Acceptance tests in MarionetteJS, we need to be aware what they are needed for and what the limitations are regarding MarionetteJS. =Challeng...") |
(→Risks) |
||
| Line 24: | Line 24: | ||
=Risks= | =Risks= | ||
* No MarionetteJS on device possible | |||
=Links= | =Links= | ||
* [Integration_vs_Acceptance#The_Solution] | * [Integration_vs_Acceptance#The_Solution] | ||
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1L1QAOuKx5pWNizMmotmyauCZ0zl3JrgsGDx0PnWxGd8/edit#gid=0] | * [https://docs.google.com/a/mozilla.com/spreadsheets/d/1L1QAOuKx5pWNizMmotmyauCZ0zl3JrgsGDx0PnWxGd8/edit#gid=0] | ||
Latest revision as of 12:42, 1 April 2015
Objective
For developing Gaia Acceptance tests in MarionetteJS, we need to be aware what they are needed for and what the limitations are regarding MarionetteJS.
Challenges Addressed
- Currently, no Gaia Acceptance tests in MarionetteJS, only Gaia UI Tests
- No MarionetteJS tests on device
The Problem
Currently, no Gaia Acceptance tests exists for MarionetteJS. There are Gaia Integration tests that fulfill this role partly, but we need a better separation between UI testing and the functional testing of the various Gaia components. The Python UI tests currently fulfill the role as Acceptance tests, but developers don't want to write tests in Python and are already used to writing integration tests in MarionetteJS.
The Solution
Pick the existing Python UI tests to move those over to MarionetteJS, but be aware of the current limitations in the MarionetteJS framework.
Timeline
Q1
- [DONE] Gaia Python Acceptance confidence refactoring [Martijn] [1]
Risks
- No MarionetteJS on device possible
Links
- [Integration_vs_Acceptance#The_Solution]
- [2]