Auto-tools/Projects/Platform Quality/External Media Tests: Difference between revisions
< Auto-tools | Projects | Platform Quality
Jump to navigation
Jump to search
m (typo) |
(Added codes for different lengths of EME tests, and for bandwidth limiting.) |
||
Line 10: | Line 10: | ||
** y - short tests using YouTube JS API on YouTube | ** y - short tests using YouTube JS API on YouTube | ||
** ym1-60 - hour-long tests using YouTube JS API on YouTube | ** ym1-60 - hour-long tests using YouTube JS API on YouTube | ||
** e - | ** e - short tests using standard video API to test EME | ||
** e-f - full tests using standard video API to test EME | |||
** *-e10s - job that is run with e10s enabled e.g. m-e10s, y-e10s | ** *-e10s - job that is run with e10s enabled e.g. m-e10s, y-e10s | ||
** *-bw - tests that runs for various bandwidths | |||
== Instructions for running locally. == | == Instructions for running locally. == |
Revision as of 21:40, 29 September 2015
firefox-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.
Results Reported to Treeherder
These are Tier-2 jobs, meaning they are visible by default but not sheriff-managed.
- Repos: mozilla-central, mozilla-beta
- Group Name: VideoPuppeteer
- Group Symbol: VP
- Jobs:
- m - short tests using standard video API on YouTube
- y - short tests using YouTube JS API on YouTube
- ym1-60 - hour-long tests using YouTube JS API on YouTube
- e - short tests using standard video API to test EME
- e-f - full tests using standard video API to test EME
- *-e10s - job that is run with e10s enabled e.g. m-e10s, y-e10s
- *-bw - tests that runs for various bandwidths
Instructions for running locally.
Please see the project's readme
How to disable an individual failing test.
Visit 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.
Contacts
maja_zf (MSE)
sydpolk (EME)
Where to file bugs
Test failures seen on Treeherder should be filed under Core::Audio/Video: Playback