Auto-tools/Projects/Firefox UI Tests: Difference between revisions
(Rework page and add all necessary information) |
m (→Goals) |
||
| Line 8: | Line 8: | ||
The goal of this project is to increase the test coverage for new features in Firefox Desktop. Especially for those features which cannot be covered by any other [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Automated_testing existing test suite]. To achieve that we will also have to continuously improve our harness and firefox-puppeteer page object model. | The goal of this project is to increase the test coverage for new features in Firefox Desktop. Especially for those features which cannot be covered by any other [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Automated_testing existing test suite]. To achieve that we will also have to continuously improve our harness and firefox-puppeteer page object model. | ||
We want that test development will become as easy as writing | We want that test development will become as easy as writing manual tests. Therefore we only want to make use of synchronous test steps, and don't force the user to understand the DOM of the browsers interface. | ||
= Dependencies / Who will use this = | = Dependencies / Who will use this = | ||
Revision as of 13:07, 4 March 2016
About
The Firefox UI tests are a collection of integration tests mainly for testing the user interface of Firefox. The tests and its harness are based on the Marionette testing framework, and enhances it for Firefox Desktop specific behavior, e.g. it adds a page object model aka Firefox-Puppeteer.
Team
This project is maintained by the Automation Crew.
Goals
The goal of this project is to increase the test coverage for new features in Firefox Desktop. Especially for those features which cannot be covered by any other existing test suite. To achieve that we will also have to continuously improve our harness and firefox-puppeteer page object model.
We want that test development will become as easy as writing manual tests. Therefore we only want to make use of synchronous test steps, and don't force the user to understand the DOM of the browsers interface.
Dependencies / Who will use this
For every feature enhancement which cannot be directly done in our own harness, we have to work together with the developers for Marionette.
The users will be:
- Firefox QE
Contribution
We welcome contributions to Firefox UI Tests! We track issues inside the Firefox UI Tests component on Bugzilla, see below for a list of open bugs.
If you have a question, jump on #automation on irc.mozilla.org and look for whimboo, maja_zf, or syd.
Source and docs
All information about how to get the source and where to find further documentation can be found on the firefox-ui-tests page on MDN.
Bug Table
| ID | Priority | Component | Summary | Assigned to |
|---|---|---|---|---|
| 1759653 | P3 | Firefox UI Tests | Consider merging firefox-ui tests with Marionette | |
| 1945351 | P5 | Firefox UI Tests | Intermittent testing/firefox-ui/tests/functional/security/test_https_first.py TestHTTPSFirst.<test-name> | marionette_driver.errors.ScriptTimeoutException: Timed out after 30000 ms | |
| 1613386 | -- | Firefox UI Tests | [meta] Remove Firefox-UI tests |
3 Total; 3 Open (100%); 0 Resolved (0%); 0 Verified (0%);