Open Bug 1062957 Opened 10 years ago Updated 2 years ago

[steeplechase] Switch tests to a chat room per test case solution

Categories

(Core :: WebRTC, defect, P5)

Product:
Core
Component:
WebRTC
Type:
defect

Tracking

()

Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: drno, Unassigned)

Details

(Whiteboard: [webrtc-mochitest],[steeplechase]) 

Currently steeplechase and the test cases them self share the same chat room on the Node.js chat server for the test framework co-ordination and the in-test signaling.
A better solution would be to have one chat room for the steeplechase co-ordination and then one chat room per test case for in-test signaling.

Note: investigate if swapping Q for ES6 Promise polyfill lib brings us any advantage.
Switching to ES6 Promises happened. No change.

Another option to solve the problem could be to have steeplechases web harness "prefix" all messages from the test case with something like the test case name. That should allow the harness on the other end should be able to not route steeplechase messages into the actual test case.
Summary: Switch steeplechase tests to a chat room per test case solution → [steeplechase] Switch tests to a chat room per test case solution
Whiteboard: [webrtc-mochitest],[steeplechase]
backlog: --- → webRTC+
Rank: 45
Priority: -- → P4
Assignee: nobody → rshenthar
Pushed to review on github.
Mass change P4->P5 to align with new Mozilla triage process.
Priority: P4 → P5
Assignee: rshenthar → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.