Confirmed users
79
edits
Auto-tools/Projects/Platform Quality/External Media Tests: Difference between revisions
Auto-tools/Projects/Platform Quality/External Media Tests (view source)
Revision as of 21:54, 18 March 2016
, 18 March 2016More formatting
m (→Automation Information: nit) |
m (More formatting) |
||
| Line 1: | Line 1: | ||
[https://dxr.mozilla.org/mozilla-central/source/dom/media/test/external | [https://dxr.mozilla.org/mozilla-central/source/dom/media/test/external External Media Tests] is a suite of Marionette Python tests for media playback in Mozilla Firefox. Its aim is to test MSE (Media Source Extensions) and EME (Encrypted Media Extensions) on specific websites such as YouTube and Netflix. | ||
== Source == | == Source == | ||
| Line 63: | Line 63: | ||
** *-bw - tests that runs for various bandwidths | ** *-bw - tests that runs for various bandwidths | ||
=== Debugging === | ==== Debugging ==== | ||
You can RDC/VNC to individual machines in pf-jenkins. (User: mozilla). When there are problems, it often helps to trigger the job from pf-jenkins, and watch it run in your VNC window. You can also launch a mozilla-build shell and run scripts yourself. You should avoid running from the Jenkins workspace directories; you should be able to get the necessary assets to reproduce the tests on a directory on the local drives. | You can RDC/VNC to individual machines in pf-jenkins. (User: mozilla). When there are problems, it often helps to trigger the job from pf-jenkins, and watch it run in your VNC window. You can also launch a mozilla-build shell and run scripts yourself. You should avoid running from the Jenkins workspace directories; you should be able to get the necessary assets to reproduce the tests on a directory on the local drives. | ||
Command-lines for jobs can be found in the pf-jenkins GUI by selecting the project and either reading through the logs, or going into the configure pane, copying, and then pasting into your shell window. | Command-lines for jobs can be found in the pf-jenkins GUI by selecting the project and either reading through the logs, or going into the configure pane, copying, and then pasting into your shell window. | ||
=== Custom Profile === | ==== Custom Profile ==== | ||
Netflix and network bandwidth limiting tests use a stored profile with custom logins and certificates installed. | Netflix and network bandwidth limiting tests use a stored profile with custom logins and certificates installed. | ||
* Windows: c:\testing\eme_profile | * Windows: c:\testing\eme_profile | ||
* Mac: /Users/mozilla/testing/eme_profile | * Mac: /Users/mozilla/testing/eme_profile | ||
=== How to disable an individual failing test on pf-jenkins. === | ==== How to disable an individual failing test on pf-jenkins. ==== | ||
Visit [http://pf-jenkins.qa.mtv2.mozilla.com:8080/ pf-jenkins] (VPN required), open the summary page of the job you want to disable and click 'Disable Project'. When a job is reported to Treeherder, its Jenkins build url and build id are listed in the Job Details pane. | Visit [http://pf-jenkins.qa.mtv2.mozilla.com:8080/ pf-jenkins] (VPN required), open the summary page of the job you want to disable and click 'Disable Project'. When a job is reported to Treeherder, its Jenkins build url and build id are listed in the Job Details pane. | ||