PeerConnectionTest.java & RTCPeerConnection.mm should be written using callbacks instead of serializing waits
Reported by firstname.lastname@example.org, Jul 22 2013
The PC unittest in Java (and in ObjC when the latter was cloned from it) was written in a faux-serial style; instead, the test should phrase its expectations via callbacks to speed it up and to make it less brittle to event delivery timing. https://code.google.com/p/chromium/codesearch#chromium/src/third_party/libjingle/source/talk/app/webrtc/javatests/src/org/webrtc/PeerConnectionTest.java&q=f:peerconnectiontest.java%20todo&sq=package:chromium&type=cs&l=323
Jul 26 2013,
Oct 15 2014,
Oct 16 2014,
Nov 4 2015,
This bug hasn't been modified for more than a year. Is this still a valid open issue?
Nov 8 2016,
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available.
[bulk-edit] Setting status to Available since it's likely that this issue shouldn't be archived yet. Also changing Pri to 3 due to long period of inactivity (indicating low priority).
Sign in to add a comment