Browser tests for getStats |
|||||
Issue descriptionChris, I was wondering if it's possible to build some integration test that would automatically find errors like bug 632457 ? It seems like using a page like https://webrtc.github.io/samples/src/content/peerconnection/audio/ with a WebDriver test and then just checking for JS errors should be a reasonably easy test to implement?
,
Aug 31 2016
Right, but then I think we should use this bug for tracking the implementation of such a browser test.
,
Aug 31 2016
Then we need to be more specific, come to think of it, I think hbos@ did add some layout tests when he fixed this.
,
Sep 1 2016
Yes, I already added a test that made sure a "nonsense" parameter would not cause a TypeError when I fixed that bug, i.e. that would catch this problem in the future.
,
Sep 1 2016
Note: There's a lot more work surrounding stats (master bug 627816 ) which will require a lot more testing, but that is tracked by those bugs.
,
Sep 1 2016
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jansson@chromium.org
, Aug 31 2016