Web Application Developers are used to being able to write automated tests for their applications and have them run with every PR and before deploying to production to give a level of confidence that things are not broken. OpenTok and real-time applications in general present new challenges when it comes to writing and running automated tests. There are challenges when it comes to getting access to microphones and cameras, testing multiple participants and installing the plugin for Internet Explorer among others.
There has been lots of work around WebRTC testing automation and our friends at rtc.io and &yet have written some great articles on the subject. However these articles don’t cover some of the specifics of testing OpenTok applications for example testing Internet Explorer and installing the OpenTok plugin for Internet Explorer. If you haven’t already I would recommend taking some time to read the articles by the folks at rtc.io and &yet before coming back to this. Also if you’re not familiar with Travis and Selenium WebDriver you might want to check those out too.
We all have a fascination with the billion dollar startups. Venture Capitalists try and identify them early, media laud them (or bring them down to earth), and early adopters claim discovery. One new technology innovation has the potential to spark the creation of more billion dollar companies, and markets are starting to pay attention. So what is WebRTC, and why is there so much interest?
It begins with recognizing the emergence of two massive trends. The first is the increasing appetite for ‘on demand’. This is evident in everything from movies to car rides, hotels, relationships to groceries to well, everything. And communications is a core part of this, just look at Meerkat and Twitter’s latest acquisition, Periscope, bringing
This post was co-authored by Gustavo Garcia Bernardo, Philipp Hancke and Charley Robinson.
When WebRTC stuff is really broken, it gets fixed very quickly.
Early in December 2015, shortly after the release of Chrome 47 to the general public, we started to notice a subtle and strange behavior in the Audio/Video of streams during our many daily meetings using WebRTC: the video occasionally wouldn’t stay caught up with the corresponding audio. As with many bugs noticed internally by developers, it took a while for any of us to believe that what we were seeing was a real issue. We call this the inverse of productive dogfooding: rather than assume we are just like our users, we can just as easily decide we are nothing like them.
The evolution of live video has spawned new and engaging ways for brands, organizations and people to connect with their audience. Whether it’s participating in a team meeting held remotely, hosting a virtual conference for hundreds of people all over the world, demo-ing a new product to customers via a webinar, or broadcasting a live stream of an event, there is no question live video is now becoming a standard feature in any business or entrepreneur’s communication toolkit.
Early December saw the roll-out of Chrome 47. When doing anything with WebRTC, this is always an interesting time. A release brings new features or may break things, like removing the getUserMedia functionality for insecure origins.
Our metrics clearly track such roll outs as seen below: