qualityRTC can conduct silent tests, collecting the information and making it available to you.
Some of these tests are always running while others are optional and include their own configuration and customization.
Table of contents
Browser Versioning and Feature Collection Test
qualityRTC collects information about the browser type, version and specific WebRTC features.
That information is automatically stored in the log.
Customization: You can decide which browsers and versions you want the test to run on. If the browser trying to run the test doesn’t match your criteria, the test will not run and an error message will be displayed.
Estimated run time: 1 second or less
Ping Test
The ping test allows pinging specific servers/locations over HTTP to determine response times. This is useful for understanding “distances” from the user.
There is a visual test widget for this as well. The silent Ping Test is meant to do the exact same thing, but collect the information only in the log and not display it to the user directly.
Estimated test time: 8 seconds
Ping All Test
The Ping All test pings all available data centers and collecting the response times.
This is used to check malformed selection of servers by bad DNS server configurations for example. It can also be used to later manually configure a user’s region based on the collected results.
Estimated test time: 25 seconds
DNS Setup Test
The DNS Setup test finds out and reports the DNS servers configured on the client’s device.
It collects and logs the IP address, location and organization of the DNS servers used.
Estimated test time: 8 seconds
GPS Location Test
qualityRTC can collect the location of the user based on GPS information. This will cause a popup message to appear to the user to share his location with the web application.
The information collected is placed in the test results log.
Estimated run time: 1 second or less
Hardware Availability Test
qualityRTC can try to figure out the hardware used when running video sessions. This includes figuring out how many cores the CPU has, the GPU makeup and if the video codec’s implementation is using hardware acceleration or not.
The information collected is placed in the test results log.
Note: The testRTC chrome extension (companion app) is also available which can provide you with even more knowledge about your webRTC environment. With the companion app installed and your qualityRTC configuration enabled for this feature, we will be able to collect more information about the user’s machine and make it available in the log of the test results.
Devices Allow Test
qualityRTC can pre-check if the user is allowing access to the microphone and/or camera.
Customization:
- You can decide if you want this test to run at all and if it should check for a microphone, a camera or both
- You can decide if you want to collect device names or not
- You can check for camera resolutions as part of this test
- Default resolutions checked are 640×480, 1280×720 and 1920×1080
- Other custom resolutions can be checked as well as part of the configuration
- When hosted in a subdomain, this checks for availability of the devices
- When hosted on your web application (by using the SDK), this checks if the user allowed access for your web application to these devices
Estimated run time: 1 second or less
Video Playback Test
qualityRTC can pre-check if the user is blocking video playback by using an external extension. This can be useful when you are providing a video calling service and want to clear out any issues that might arise due to disabled video elements.
Customization: This test is optional. We can set it up for you if needed.
Estimated run time: 1 second or less
Local Storage Test
qualityRTC can collect information from the browser’s local storage and log it as part of the test.
This is only useful if you are using our SDK and integrating this in your web application.
Estimated run time: 1 second or less
TURN CONNECTIVITY Test
The TURN CONNECTIVITY test widget can also be configured to run silently if needed.
Traceroute test in Electron
Traceroute testing is a network diagnostic tool that traces the path a packet takes from your computer to a destination server. It helps in identifying the network route, revealing the IP addresses of intermediate hops, and measuring the round-trip times (RTT) between each hop. This information is valuable for diagnosing network issues and optimizing connectivity. The results of a traceroute test include the following information for each hop in the traceroute journey.
- Host data: The IP address of the hop.
- RTT: The time it takes for a packet to travel from your computer to the hop and back.
This information is automatically stored in the log.
Availability: This test is only available when you package qualityRTC inside an Electron application, since it requires functionality not available in web browsers.
Customization: You need to supply a list of domains which will be added to the traceroute test. Each domain will then provide traceroute results in the log when a test is run.
Estimated run time: Hard to say. Runtime can vary from one URL to another. Depending on the amount of URLs and the number of hops they are taking It can take anywhere between 15 secs to several minutes to run.