The video below shows an example of how I look at test results:
- Look at the error message shown on the main test results page. It will tell you which probe “failed first”
- If there’s media, you can check the media on that main test results page as well to figure out what went wrong
- Drill down to the faulty probe(s)
- Check the error and the Notifications tab – this tab automatically collects all warnings and errors from across the logs testRTC has access to
- Look at the screenshots in the Media tab. They may give you a hint of the problem
- Look at the Performance tab to see if there are any issues with the CPU. High jitter and packet loss can be caused due to high CPU utilization
- Check the Advanced WebRTC Analytics if you need to drill down further into peer connection configuration, ICE candidate pairs or the actual event log of the WebRTC API calls that took place