Loop/Automated Testing: Difference between revisions
(Initial fill-out of page) |
(Add information about the notifications list) |
||
| Line 1: | Line 1: | ||
== | == Test Suites == | ||
Loop has various different sections, where different tests are run. This page is intended to bring these together. | Loop has various different sections, where different tests are run. This page is intended to bring these together. | ||
== Functional Tests == | === Functional Tests === | ||
These are intended to test the whole system. | These are intended to test the whole system. | ||
| Line 13: | Line 13: | ||
* UI: TBD | * UI: TBD | ||
== Desktop == | === Desktop === | ||
Desktop tests are automatically run and displayed on the [https://treeherder.mozilla.org/ treeherder system]. | Desktop tests are automatically run and displayed on the [https://treeherder.mozilla.org/ treeherder system]. | ||
== Loop-Server == | === Loop-Server === | ||
The Loop-server runs its tests in Travis. Details of the Travis integration can be found in the [https://github.com/mozilla-services/loop-server repository]. The github homepage for the repository also includes a link to the state of the Travis builds. | The Loop-server runs its tests in Travis. Details of the Travis integration can be found in the [https://github.com/mozilla-services/loop-server repository]. The github homepage for the repository also includes a link to the state of the Travis builds. | ||
== Loop-client == | === Loop-client === | ||
Most of the automated tests are run as part of the Desktop tests (see above). | Most of the automated tests are run as part of the Desktop tests (see above). | ||
| Line 29: | Line 29: | ||
* Code: https://github.com/mozilla/hello-tests/ | * Code: https://github.com/mozilla/hello-tests/ | ||
* UI: https://webqa-ci.mozilla.com/view/Hello/ | * UI: https://webqa-ci.mozilla.com/view/Hello/ | ||
== Notifications == | |||
For tests that don't display results on treeherder, there is a email list (firefox-hello-test-notifications) that can be subscribed to for receiving updates. | |||
If you're not a mozilla employee, talk to Standard8 or dmose ([https://wiki.mozilla.org/Loop#Communication_Channels on irc]) if you need to join the list (this is due to limitations in our groups system). | |||
Revision as of 15:38, 2 July 2015
Test Suites
Loop has various different sections, where different tests are run. This page is intended to bring these together.
Functional Tests
These are intended to test the whole system.
They are currently run against latest nightly and latest loop-server.
- Functional test source code: http://mxr.mozilla.org/mozilla-central/source/browser/components/loop/test/functional/
- Test harness code: https://github.com/nils-ohlmeier/hello-e2e-tests
- UI: TBD
Desktop
Desktop tests are automatically run and displayed on the treeherder system.
Loop-Server
The Loop-server runs its tests in Travis. Details of the Travis integration can be found in the repository. The github homepage for the repository also includes a link to the state of the Travis builds.
Loop-client
Most of the automated tests are run as part of the Desktop tests (see above).
There are additional tests run against different browsers that ensure the expected functioning of the standalone UI:
Notifications
For tests that don't display results on treeherder, there is a email list (firefox-hello-test-notifications) that can be subscribed to for receiving updates.
If you're not a mozilla employee, talk to Standard8 or dmose (on irc) if you need to join the list (this is due to limitations in our groups system).