Open Bug 1193289 Opened 9 years ago Updated 2 months ago

Add getUserMedia constraints tests for bug 1191298

Categories

(Core :: WebRTC: Audio/Video, defect, P3)

42 Branch
defect

Tracking

()

REOPENED

People

(Reporter: jesup, Assigned: ng)

References

Details

Attachments

(1 obsolete file)

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).
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
Assignee: ngrunbaum → na-g
Is still relevant?
Flags: needinfo?(na-g)
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3

Guessing it is not still relevant, clearing old needinfo.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(na-g)
Resolution: --- → WONTFIX

Er... do we have test coverage here? If not, how is this not relevant?

Status: RESOLVED → REOPENED
Flags: needinfo?(jib)
Resolution: WONTFIX → ---

With bug 1537986, fake devices now have constrainable properties enough to satisfy wpt coverage for constraints, including for getSettings().

They don't cover all possible constraints, but doing so in a fake device give diminishing returns.

Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Flags: needinfo?(jib)
Resolution: --- → FIXED

Didn't mean to close it without discussion.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Jan-Ivar, if you're happy with the state of testing here, that works for me.

Severity: normal → S3
Attachment #9383132 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: