If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Add getUserMedia constraints tests for bug 1191298

NEW
Assigned to
(NeedInfo from)

Status

()

Core
WebRTC: Audio/Video
P2
normal
Rank:
17
2 years ago
12 days ago

People

(Reporter: jesup, Assigned: ng, NeedInfo)

Tracking

(Depends on: 1 bug)

42 Branch
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
Add tests for the case in bug 1191298.  This requires support in the fake cameras/loopback devices on the testers so this can be testable (bug 1088621).
(Reporter)

Updated

2 years ago
backlog: --- → webRTC+
Rank: 25
Priority: P1 → P2
I'm much more comfortable with this being a P1 -- to get tests in (whether they are unit tests or mochitests).  I'd be fine with writing unit tests now to bridge the gap until we have support on the testers to write mochitests.
Rank: 25 → 15
Priority: P2 → P1
Jan-Ivar - how hard would it be to add constraints to the fake devices, or to write a unit test (that has to run on a machine with real audio/video hardware)?

Assigning to Jan-Ivar for now
Assignee: nobody → jib
Flags: needinfo?(jib)
I should be able to make them pretend to have capabilities fairly quickly. Whether the resulting output actually changes we'll have to see how easy/useful that is.
Flags: needinfo?(jib)
That's Bug 1088621 btw, which this bug depends on (I thought I was commenting on that one).
Assignee: jib → ngrunbaum
Rank: 15 → 17

Updated

3 months ago
Assignee: ngrunbaum → na-g

Comment 5

3 months ago
Is still relevant?
Flags: needinfo?(na-g)
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
You need to log in before you can comment on or make changes to this bug.