TestingRTC FAQ

There are several reasons why we’ve decided in to rely on real browsers for our testing and monitoring products. Here you will find a list of those reasons. Applications using WebRTC are more likely than not to work inside web brows...

testRTC can get to high number of probes count for its testing . That said, since we use real browsers that require multiple CPU cores to work effectively at large scale, this becomes expe...

testRTC offers firewall profiles to check TURN connectivity. Here you will find the details of each firewall profile configuration and the ports it keeps open. Note: You can use .rtcSetNetwork() and .rtcSetNetworkProfile() to dynami...

bitrate units bitrate units are bytes. We check channel.bytes.average for bitrate, for channel.bitrate.drop we take channel.bytes.average * 1,000 as average and divide by max drop and * 100 for percentage. framera...

testRTC has two different techniques to collect its WebRTC metrics: By using webrtc-internals By using getstats webrtc-internals If you open a tab in your Chrome browser and direct it to chrome://webrtc-internals/, you will b...

You can use the #chrome-cli run option to set the probe’s browser user agent string to whatever you want. Here’s an example:#chrome-cli:user-agent="Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, lik...

testRTC allows you to set your own customer environment variables in running test scripts via the APIs. This gives more flexibility when executing the commands from CI/CD or other test suite environments. You can use environment vari...

testRTC runs in the cloud by default. The probes we use that simulate live users come from the public internet. As such, if your WebRTC implementation is installed on a local network, on a machine or a lab, and you need it tested, th...

All probes allocated by testRTC use an NTP server to synchronize their clocks. The server in use is Google’s NTP (more about it here: http://time.google.com/). If you configure your servers to the same NTP servers, you will be able t...

testingRTC offers a robust testing service for WebRTC applications. To be able to do this successfully, we run the service on high performance machines running in the cloud. Each probe used in the test has enough processing a...

Also known as NWTL, the Nightwatch Testing Library is a powerful utility library for Nightwatch that makes figuring out and finding the elements in your UI that needs to be clicked, filled or waited upon clearer and cleaner. As this...

At times, our clients run their services in restricted networks, where they cannot have anyone from the public internet connect. This makes using our testing service a challenge, since by default, our service will allocate a ...

For some scenarios, you just want to validate something that isn’t directly related to WebRTC. testRTC by default assumes that you want WebRTC sessions, so if it can’t find any WebRTC connection with some audio or video data in it in...

When defining a test script in testRTC you can add multiple profiles to be used in your test:There are two different allocation algorithms that you can use: Round-robin Random Round-robin probes allocation By default, profiles are...

testRTC collect the console log of the browser. This is a great tool for debugging application specific issues. By default, we don’t collect the VERBOSE logs – these are just too… verbose. If you need to collect them, you can...

Running a test script in testingRTC (or upRTC) means that one or more virtual machines are allocated for your WebRTC test script to execute. Using these virtual machines is costly, so there is a need to make sure that they are on...