Connectivity test types
The Qualoo testing process involves running multiple groups of connectivity tests. These tests, performed by the Test Nodes in the Qualoo network, cover a variety of aspects of internet performance to provide comprehensive data about the quality of experience (QoE). Below are some examples of connectivity test types:
Quality of Service (QoS): This test measures data between the user and major exchange points globally. Metrics include packet loss, latency, jitter, and throughput.
DNS Tests: These tests assess the performance of the Domain Name System (DNS), which translates domain names to IP addresses. These tests may be performed against different common DNS providers to evaluate their reliability and speed.
HTTP Tests: These tests evaluate the performance of Hypertext Transfer Protocol (HTTP), which is the foundation of any data exchange on the web. HTTP tests might be performed against multiple websites to assess the loading speed and efficiency of data transfer. Metrics include total page load time, time to open TCP port, download speed, number of elements downloaded, authentication time (SSL handshake), and hello time (time to first data packet).
Bandwidth Tests: These tests measure the speed of internet connectivity. They can be performed against multiple servers in different locations to assess the capacity and speed of the internet connection.
Trace Route: This test measures latency to hops along common routes.
Video Streaming Tests: These tests are designed to assess the quality of video streaming on the network, which can be a significant factor in the overall user experience, especially for services like Netflix or YouTube.
Mobile Signal Tests: These tests are specific to Mobile Test Nodes and measure the strength and reliability of the mobile signal.
These tests cover a wide range of connectivity aspects, providing comprehensive data on the performance of internet connections. This allows Qualoo to deliver actionable insights to clients.
The tests run on each Test Node may differ based on the type of Test Node and other considerations. For example, mobile signal tests can only be run on Mobile Test Nodes. Additionally, tests with higher bandwidth requirements, like bandwidth tests or video streaming tests, may not be run as frequently to minimize the impact on users' data. This approach ensures a balanced and effective testing process that provides valuable data without excessively burdening users' resources.
Last updated