Re: Call for Consensus (CfC) on Adoption of the "Media Capture Automation" specification

Some info can be found in slides of the June 4 2020 WebRTC interim: slides 13 and 14 of https://docs.google.com/presentation/d/1NOAcGOAx6jZphmw35baBh2P9WwY9ZuynetBLHSFBphw/edit#slide=id.g7761f703bc_0_7
There are two main use cases, all related to testing:
- Testing of applications
 - Use of mock devices in applications has some benefits in terms of repeatability, privacy. There is no browser generic API for mocks.
 - Applications cannot really test how their scripts would react to setups with no camera, no microphone. Or to changes in the setup: new camera is added, being used camera is removed.
- Testing of browsers
        - We know some APIs (getUserMedia, applyConstraints) may have browser specific behaviors and increasing consistency would be good.
 - WPT is very limited in how it is testing various aspects of these APIs
        - Browsers currently have some tests, but they are browser specifics

It seems like a good idea to add a scope section in the spec.


> On 29 Sep 2020, at 08:55, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote:
> 
> I would like to see some info about what use case this spec is enabling (my guess would that it is related to testing, but I find no info in the spec or the github repo).
>  
> Br,
> Stefan
>  
> From: Bernard Aboba <Bernard.Aboba@microsoft.com <mailto:Bernard.Aboba@microsoft.com>>
> Date: Wednesday, 23 September 2020 at 19:06
> To: "public-webrtc@w3.org <mailto:public-webrtc@w3.org>" <public-webrtc@w3.org <mailto:public-webrtc@w3.org>>
> Subject: Call for Consensus (CfC) on Adoption of the "Media Capture Automation" specification
> Resent from: "public-webrtc@w3.org <mailto:public-webrtc@w3.org>" <public-webrtc@w3.org <mailto:public-webrtc@w3.org>>
> Resent date: Wednesday, 23 September 2020 at 19:04
>  
> This is a Call for Consensus (CfC) on Adoption of the "Media Capture Automation" specification as a WEBRTC WG deliverable. 
> The specification is here: 
> https://youennf.github.io/media-capture-automation/media-capture-automation.html <https://protect2.fireeye.com/v1/url?k=cd1dba7b-93bd14b6-cd1dfae0-86073b36ea28-31032005c2c23e73&q=1&e=8df7de18-aff6-47a2-9dd2-8a60ad2b7e5d&u=https%3A%2F%2Fyouennf.github.io%2Fmedia-capture-automation%2Fmedia-capture-automation.html>
>  
> The GitHub repo is here: 
> https://github.com/youennf/media-capture-automation <https://protect2.fireeye.com/v1/url?k=dd8667c0-8326c90d-dd86275b-86073b36ea28-91fb30e3b2e76066&q=1&e=8df7de18-aff6-47a2-9dd2-8a60ad2b7e5d&u=https%3A%2F%2Fgithub.com%2Fyouennf%2Fmedia-capture-automation>
>  
> The CfC will last for two weeks and will end on Wednesday, October 7, 2020. 
>  
> In response, please state one of the following: 
> ·         I support adopting the "Media Capture Automation" specification as a WEBRTC WG deliverable. 
> ·         I object to adopting the "Media Capture Automation" specification as a WebRTC WG deliverable, due to issues filed in open bug <#number>.