Auto-tools/Projects/Firefox UI Tests: Difference between revisions
(Rework page and add all necessary information) |
(Update for new projects and owners) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
= Team = | = Team = | ||
This project is maintained by the [[QA/Automation|Automation Crew]]. | This project is maintained by the [[QA/Automation|Automation Crew]], and the primary contact is Henrik Skupin. | ||
= Goals = | = 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 [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 = | ||
| Line 19: | Line 19: | ||
We welcome contributions to Firefox UI Tests! We track issues inside the [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&component=Firefox%20UI%20Tests&product=Testing&list_id=12889451 Firefox UI Tests component on Bugzilla], see below for a list of open bugs. | We welcome contributions to Firefox UI Tests! We track issues inside the [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&component=Firefox%20UI%20Tests&product=Testing&list_id=12889451 Firefox UI Tests component on Bugzilla], see below for a list of open bugs. | ||
If you have a question, jump on [irc://irc.mozilla.org/automation #automation] on irc.mozilla.org and look for whimboo, maja_zf | If you have a question, jump on [irc://irc.mozilla.org/automation #automation] on irc.mozilla.org and look for whimboo, or maja_zf. | ||
== Source and docs == | == Source and docs == | ||
More information about the tests and how to run those can be found in the [https://developer.mozilla.org/en-US/docs/Mozilla/QA/firefox-ui-tests Mozilla Developer Network]. | |||
== Active and Planned Projects == | |||
The currently most important projects for the firefox-ui-tests are the following: | |||
* Bug 1272236 - Let Mozmill-ci execute functional and update tests for Nightly builds on Linux64 via TaskCluster | |||
* Bug 1272228 - Make Firefox-ui-tests results from TaskCluster Tier-1 or Tier-2 on Treeherder | |||
* Bug 1272145 - Move Firefox-ui-tests from testing/firefox-ui-tests/tests to individual browser/toolkit components | |||
== Bug Table == | == Bug Table == | ||
Latest revision as of 16:23, 20 May 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, and the primary contact is Henrik Skupin.
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, or maja_zf.
Source and docs
More information about the tests and how to run those can be found in the Mozilla Developer Network.
Active and Planned Projects
The currently most important projects for the firefox-ui-tests are the following:
- Bug 1272236 - Let Mozmill-ci execute functional and update tests for Nightly builds on Linux64 via TaskCluster
- Bug 1272228 - Make Firefox-ui-tests results from TaskCluster Tier-1 or Tier-2 on Treeherder
- Bug 1272145 - Move Firefox-ui-tests from testing/firefox-ui-tests/tests to individual browser/toolkit components
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%);