Closed
Bug 688178
Opened 13 years ago
Closed 12 years ago
Import WebRTC library into core [tracking bug]
Categories
(Core :: WebRTC, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jesup, Unassigned)
References
Details
(Whiteboard: [WebRTC], [qa-])
Tracking bug for all the other bugs to be filed to get WebRTC into the branch
Comment 1•13 years ago
|
||
How are we going to track upstream changes once we have a fork checked in?
What is the plan for ensuring the code that we have for this is instrumented well enough that we can do meaningful tests with it? Is there a test framework already in place and I'm missing the proper bug? Thanks.
Reporter | ||
Comment 3•13 years ago
|
||
There is an internal test framework in the imported code. We obviously will need additional testing and test code. No bug has been created for this yet - thanks for the reminder. We have been in touch with the QA group by email to give them a heads-up.
Some aspects may be tough to test automatically due to the need for it to interact across a network connection with another instance.
Updated•13 years ago
|
Reporter | ||
Comment 4•13 years ago
|
||
Remaining work is mostly removing parts of the imported code, or turning off building of it, and moving test code into appropriate bits.
Reporter | ||
Updated•13 years ago
|
Assignee: rjesup → nobody
Component: Video/Audio → WebRTC
QA Contact: video.audio → webrtc-general
Updated•13 years ago
|
QA Contact: jsmith
Updated•12 years ago
|
Whiteboard: [WebRTC]
Comment 5•12 years ago
|
||
Initial import has been done, closing for now. followup bugs should be filed as needed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Whiteboard: [WebRTC] → [WebRTC], [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•