Support & information center

testRTC July 2020 Release Notes

Facelift

In this round of our facelift, we focused on the top navigation bar. We now show a consistent view of the page title and breadcrumbs.

Filters

When applying filters on lists throughout testRTC, we now generate URLs. This allows you to return back to the filtered view you created and even share it with your teammates.

Testing & Monitoring

Analysis

  • Analysis charts on the test level now offer zoom and synchronization capabilities, making the analysis of the results much more powerful
  • We’ve revamped the ICE candidates pairs table in the Advanced WebRTC Analytics view, making it clearer and more detailed

Testing

Two new columns were added to the Scripts list

  • Last Modified column, making it easy to work on the most recently modified scripts
  • The flag at the rightmost column, indicating the status result of the last time the script was executed

The test script editor now shows most recent test run results for the given script, making it easier to check previous results

APIs

  • Updated our API doc environment and made it more modern
  • Fixed a bug when retrieving screenshots of test results

qualityRTC: Network Testing

New tests

  • We can now conduct a new test that check if the DNS configuration of the machine selects the optimal data center to work with
    • We’ve noticed that in some cases, DNS providers such as Cloudflare don’t work well with AWS Route 53, which may cause your service to end up with wrong routing schemes, reducing media quality
    • To that end, we will now indicate if we find such errors, if this test is configured on your account

New features

  • qualityRTC user pages now load faster. We’ve made them selectively load just modules that are needed and only at the moment they are needed. You’ll see a significant improvement there
  • We’ve added a new region URL parameter to qualityRTC users who rely on Twilio for their infrastructure. This enables checking against a specific region instead of using the default geolocation mechanism
  • We now show all ping results in the logs, if this test is enabled for the account

probeRTC: Zero install network probes

  • Probes are now displaying the active probes first and in alphabetical order by default. This should make it easier for clients with a large number of probes to manage them better
  • We’ve added knowledge base articles to all graphs and detailed logs in probeRTC, making it easier for support teams to use and share with end users

Was this article helpful?

Related Articles