613152af11
The peer connection loopback test could catch regressions too, but it's too slow to run on downstream ARM emulators. I'm adding a test here that just makes sure we can load the JNI and init audio/video engines in WebRTC. This test overlaps in functionality with the existing tests, but we need it anyway since all existing tests are too timing-sensitive. Removes resources from the test; they're awkward downstream and we don't really need them anyway. BUG=b/32820229 Review-Url: https://codereview.webrtc.org/2506603002 Cr-Commit-Position: refs/heads/master@{#15101}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others. This page is maintained by the Google Chrome team.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc