We need better replaceTrack testing
Categories
(Core :: WebRTC: Signaling, task, P3)
Tracking
()
People
(Reporter: bwc, Unassigned)
References
Details
We need replaceTrack testing that:
Checks that replaceTrack(null) does not cause mute events.
Checks that replaceTrack(non-null) does not cause unmute events.
Checks that replaceTrack(null) actually sends black frames/silence (based on inbound-rtp stats, probably?).
And probably other things.
|
||
Comment 1•1 year ago
•
|
||
I can also think of a test that non-null -> replaceTrack(non-null) does switch to the new track.
In addition to checking inbound-rtp we should check that the expected pixels get rendered.
Tests for replacing a track with another with different properties would be good too.
For video: tracks with different video dimensions, image format (if we can?).
For audio: tracks with different samplerate and channel count
And why not
enabled->replaceTrack(!enabled), and
!enabled->replaceTrack(enabled)
ditto with muted
Description
•