Test WebRTC using automated web-platform-tests |
|||||
Issue descriptionThis is a tracking bug for the work that would be required to upstream all WebRTC tests to web-platform-tests and run them automatically on unmodified Chrome release builds, as part of the web-platform-tests Travis jobs and for https://wptdashboard.appspot.com/
,
Apr 14 2017
I think Chrome is pretty good on flags for that. The three most important ones are: --use-fake-ui-for-media-stream (skips permission prompt) --use-fake-device-for-media-stream (hello mrs pacman) --mute-audio (mutes audio, no more beeps when running tests locally) https://testing.googleblog.com/2014/09/chrome-firefox-webrtc-interop-test-pt-2.html and part 1 describe the basic setup. The only thing missing on my wishlist is a way to control whether a fake audio/video device is present.
,
Apr 17 2017
Is there any way to cause the permissions prompts to be denied?
,
Apr 18 2017
my webdriver wrapper has it all: https://github.com/fippo/testbed/blob/master/webdriver.js#L68 Fiddles with the chrome profile in bad ways :-)
,
Apr 18 2017
#3, to cause permissions to be denied one can use --use-fake-ui-for-media-stream=deny
,
Apr 24 2017
,
Apr 26 2017
That is still only a workaround. You do not replicate the way a real user would use the code. The final answer would be to be able to interact with security prompt directly with webdriver. That require an extension of the spec that is currently being done.
,
Apr 26 2017
,
Apr 27 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 2 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by foolip@chromium.org
, Apr 14 2017