diff --git a/webrtc/test/w3c/getusermedia_conformance_test.html b/webrtc/test/w3c/getusermedia_conformance_test.html index 3b58301ca2..8a95032e26 100644 --- a/webrtc/test/w3c/getusermedia_conformance_test.html +++ b/webrtc/test/w3c/getusermedia_conformance_test.html @@ -1,7 +1,16 @@ +
-This page contains a foundation of conformance tests that can be expanded to cover most things in the W3C specification of the Media Capture and Streams API.
-VERSION: These tests are based on the W3C Editor's Draft of 25 September - 2012. +
VERSION: These tests are based on the W3C Editor's Draft of August 24th, + 2013 + (http://dev.w3.org/2011/webrtc/editor/archives/20130824/getusermedia.html)
STATUS: In its current state, it only performs simple checks on the various attributes and methods of the objects exposed by the API. There's not much - functionality tested so far.
-PREREQUISITES: You must have a webcam available on the machine that the - test is executed at.
-PREFIX: These tests currently utilizes the
webkitprefix, so - that will have to changed in order to to test conformance with the actual - standard! -
SPEC: - http://dev.w3.org/2011/webrtc/editor/getusermedia.html
+ functionality tested so far. The spec doesn't define if an attribute shall be + owned by the object itself (assert_own_propety) or if it shall be
+ inherited (assert_inherits). Since testharness.js doesn't offer
+ any generic function that covers both, the method for verification is
+ currently chosen according to the current Chrome implementation.
+ PREFIXES: These tests currently utilizes the adapter.js
+ script, which handle the prefixes used by different browsers.
HOW TO RUN: The easiest way is to tell your browser to: +
--use-fake-ui-for-media-stream in
+ Chrome)--use-fake-device-for-media-stream in Chrome)--allow-file-access-from-files in Chrome)