Status

()

defect
P4
normal
Rank:
35
5 years ago
2 years ago

People

(Reporter: rgauthier, Assigned: pkerr)

Tracking

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
We need to know if the about:webrtc page is broken.
For now we rely on the loop's React version.
Because React is updated some time to time, the about:webrtc page can break.

Thus, we need a test telling us if everything is allright.
(Reporter)

Updated

5 years ago
Assignee: nobody → rgauthier
Taking over this after discussing it with tOkeshu.
Assignee: rgauthier → nperriault
Adds a simple mochitest to ensure the about:webrtc page isn't entirely broken.
Attachment #8545240 - Flags: feedback?
Comment on attachment 8545240 [details] [diff] [review]
Added mochitest to ensure the about:webrtc page isn't broken.

Grmbl, totally forgot to add a name next to the feedback flag :(
Attachment #8545240 - Flags: feedback? → feedback?(mdeboer)
Comment on attachment 8545240 [details] [diff] [review]
Added mochitest to ensure the about:webrtc page isn't broken.

Clearing feedback for this moment, because pkerr is doing overlapping work in bug 1100508. Depending on the outcome of that bug, which should include tests as well.
Attachment #8545240 - Flags: feedback?(mdeboer)
Depends on: 1100508
Paul - with your redo, do we need to add more coverage or are we good?
Assignee: nperriault → pkerr
backlog: --- → webRTC+
Rank: 35
Flags: needinfo?(pkerr)
Priority: -- → P3
(Assignee)

Comment 6

4 years ago
We are not good here. We need to create a test that will catch both e10s and non-e10s regressions. Probably a new mochitest.
Flags: needinfo?(pkerr)
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
You need to log in before you can comment on or make changes to this bug.