Open Bug 850461 Opened 12 years ago Updated 2 years ago

Enhance existing data channel smoke tests in mochitest to heavily test Data Channel attributes

Categories

(Core :: WebRTC, defect, P4)

Product:
Core
Component:
WebRTC
Type:
defect

Tracking

()

Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: jsmith, Unassigned)

References

Details

(Whiteboard: [tests])

After we land support for basic smoke test coverage for data channels, we should enhance the existing tests to heavily drill into the attributes of the data channel object throughout the execution of the smoke tests. Attributes to analyze include: - label - reliable - readyState - bufferedAmount - binaryType If this ends up getting implemented as part of the smoke tests, then feel free to close this bug after the smoke tests land.
Blocks: dc-tests
Putting ? on this one cause this technically falls into the smoke tests domain of automation.
Priority: -- → P2
Whiteboard: [WebRTC][blocking-webrtc?]
Since you are already looking at data channels already - Henrik, do you want to take this one as well as the next bug to work on after data channel smoke tests land?
My way how to work through requests will be the severity setting in individual mochitest bugs. So if all P1 are done, I can have a look for sure.
Whiteboard: [WebRTC][blocking-webrtc?] → [WebRTC][blocking-webrtc+]
Assignee: nobody → hskupin
Whiteboard: [WebRTC][blocking-webrtc+] → [WebRTC][blocking-webrtc-][tests]
Per triage today, attribute analysis isn't a critical "smoke test" of the WebRTC feature set. Bumping this to P3 and unassigning.
Assignee: hskupin → nobody
Priority: P2 → P3
Dependent on initial landing in bug 796894. There's more attributes to analyze post landing of that bug.
Depends on: 796894
backlog: --- → webRTC+
Rank: 35
Whiteboard: [WebRTC][blocking-webrtc-][tests] → [tests]
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.