582367f251
I intend here to put these up for review on W3C. This moves the tests to use the W3C-style vendor prefix handling and updates the tests to the latest drafts. This yields 44 Pass 24 Fail and 13 pass 54 fail 1 timeout on Firefox. As far I can tell all failures are correct; in particular FF media media stream tracks do not adhere to the standard. Also I can't get FF to get a remote video up in the peerconnection test, just the local one. BUG=webrtc:3455 R=kjellander@webrtc.org Review URL: https://webrtc-codereview.appspot.com/14639004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6370 4adac7df-926f-26a2-2b94-8c16560cd09d
68 lines
3.1 KiB
HTML
68 lines
3.1 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
|
<!--
|
|
Copyright (c) 2013 The WebRTC project authors. All Rights Reserved.
|
|
|
|
Use of this source code is governed by a BSD-style license
|
|
that can be found in the LICENSE file in the root of the source
|
|
tree. An additional intellectual property rights grant can be found
|
|
in the file PATENTS. All contributing project authors may
|
|
be found in the AUTHORS file in the root of the source tree.
|
|
-->
|
|
<html>
|
|
<head>
|
|
<title>getUserMedia Browser Conformance Test</title>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
|
<meta charset="utf-8">
|
|
</head>
|
|
|
|
<!--
|
|
To quickly iterate when developing this test, make sure you select
|
|
'Always allow this site to use this webcam' option in the dropdown menu of
|
|
Chrome when it's requesting access to your webcam.
|
|
Notice that this requires the site you're browsing to use HTTPS.
|
|
-->
|
|
|
|
<body>
|
|
<h1>Conformance test for the Media Capture and Streams API</h1>
|
|
<p>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.</p>
|
|
<p>VERSION: These tests are based on the W3C Editor's Draft of 07 May,
|
|
2014
|
|
(<a href="http://dev.w3.org/2011/webrtc/editor/archives/20140507/getusermedia.html">http://dev.w3.org/2011/webrtc/editor/archives/20140507/getusermedia.html</a>)
|
|
<p>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. The spec doesn't define if an attribute shall be
|
|
owned by the object itself (<code>assert_own_propety</code>) or if it shall be
|
|
inherited (<code>assert_inherits</code>). 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.</p>
|
|
<p>HOW TO RUN: For Chrome, do this:
|
|
<ul>
|
|
<li>Provide a fake webcam (<code>--use-fake-ui-for-media-stream</code> in
|
|
Chrome)</li>
|
|
<li>Automatically allow access to the webcam
|
|
(<code>--use-fake-device-for-media-stream</code> in Chrome)</li>
|
|
<li>Allow loading HTML files from disk
|
|
(<code>--allow-file-access-from-files</code> in Chrome)</li>
|
|
</ul>
|
|
Then just load this HTML file to execute the tests.</p>
|
|
<p>For Firefox, set the media.navigator.permission.disabled property to true
|
|
about:config. You must have a webcam and microphone available on the system.
|
|
</p>
|
|
|
|
<div id="log"></div>
|
|
<video id="local-view" autoplay="autoplay" muted="true"></video>
|
|
|
|
<!-- These files are in place when executing on W3C. -->
|
|
<script src="/resources/testharness.js"></script>
|
|
<script src="/resources/testharnessreport.js"></script>
|
|
<script src="/common/vendor-prefix.js"
|
|
data-prefixed-objects= '[{"ancestors":["navigator"], "name":"getUserMedia"},
|
|
{"ancestors":["window"], "name":"RTCPeerConnection"}]'
|
|
data-prefixed-prototypes='[{"ancestors":["HTMLMediaElement"],"name":"srcObject"}]'></script>
|
|
|
|
<script src="getusermedia_conformance_test.js"></script>
|
|
</body>
|
|
</html>
|