Loop/Automated Testing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Add information about the notifications list)
m (Link: Loop Test)
 
Line 35: Line 35:


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).
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).
== Reference ==
* [[Loop/Test]]

Latest revision as of 17:31, 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.

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).

Reference