Hi Everyone,
Now that we've finished off an initial run of developing a refactored,
reusable test framework for WebRTC, I'd like to push forward with
tracking and taking automation requests for various parts of WebRTC.
I've built out a tree under bug 749522 that demonstrates the bugs being
tracked for mochitest development on the WebRTC APIs
(https://bugzilla.mozilla.org/showdependencytree.cgi?id=749522&hide_resolved=1).
In this tree, I've started prioritizing these automation requests by the
following buckets in alignment with the global WebRTC triage:
* P1 = automation bustage - needs critical attention. Typically
usually ends up being a blocker for a targeted release.
* P2 = automation request highly needed. Typically focuses on bare
bone, basic flows involving the WebRTC APIs. May block a targeted
release. These will typically be set to blocking-webrtc? for triage
analysis.
* P3 = automation request want. Typically this focuses on more complex
or error flows involving the WebRTC APIs. Won't ever block a
targeted release, so you'll see this set to blocking-webrtc- by default.
* P4 = automation request low importance. Typically focuses on areas
we could automate, but the value of the automation seems quite low.
Won't ever block a release either.
* P5 = automation request for unimplemented feature that doesn't block
a WebRTC release currently. This focuses on WebRTC automation around
features that do not currently block a targeted release that are
also not implemented (e.g. stats, identity).
Now the list built under the tree of bug 749522 is just a start from
brainstorming that's gone on for automation ideas for WebRTC. There's a
bunch more automated tests we could add that do not have bugs filed for
automation requests yet. If you have an idea for some automated tests
you think we need for the WebRTC APIs that is not covered by existing
automation or bugs currently filed, then file a bug in the WebRTC
component for the test automation you think is needed. We'll work to
prioritize new testing requests and work off the list by priority.
If you have any questions or comments, please let me know.
--
Sincerely,
Jason Smith
Desktop QA Engineer
Mozilla Corporation
https://quality.mozilla.com
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
