testRTC allows you to set your own machine profile variables when running test scripts via the APIs.
You can use machine profiles via the API to set the following parameters:
- Browser: Choose the executed agents’ browser type and version.
- Location: Choose the probes’ geographical location.
- Media: Choose media (video and audio) that will be used in a test. You can choose based on the media resolution and bandwidth.
- Network Profile: Choose the probes’ network profile. The network profile is composed of different criteria, such as the agents’ bandwidth, latency and drop packets percentage.
- Firewall Profile: You can select the networking ports for both open and closed probes, as well as define packet filtering rules. The firewall profile allows you to simulate various networking setups, including different firewall and NAT rules.
Table of contents
Example values for a machine profile:
{
"browser": "linux-chrome-stable",
"location": "East-US",
"media": "VOA-VGA.mp4",
"network": "No throttling",
"firewall": "FW_NO_FW",
}
Browser options
Choose one of the following values from the ‘Browser’ column and add it to your script as can be seen in the example above – “browser”: “linux-chrome-stable”
Browser |
linux-chrome-stable |
linux-chrome-beta |
linux-chrome-unstable |
linux-firefox-stable |
Location options
Choose one of the following values from the ‘Location’ column and add it to your script as can be seen in the example above – “location”: “East-US”
Location |
East-US |
West-US |
Europe |
Asia |
Japan |
Australia |
Brazil |
Canada |
India |
London |
Media options
Choose one of the following values from the ‘Media’ column and add it to your script as can be seen in the example above – “media”: “VOA-VGA.mp4”
Media | Video | Audio |
VOA-VGA.mp4 | 640×480 @ 30 fps | 121 Kbps |
KrankyGeek-2-1080p.mp4 | 1920×1080 30 fps | 173 Kbps |
Salsa-720p.mp4 | 1280×720 30 fps | 192 Kbps |
Tame_Impala-320x240p | 320×240 | 128 Kbps |
VOA-VGA04 | 640×480 30 fps | 121 Kbps |
VOA-VGA10 | 640×480 30 fps | 121 Kbps |
VOA-audio-only.mp4 | N/A | 98 Kbps |
WebRTC-Tutorial-Audio10 | N/A | 98 Kbps |
WebRTC-Tutorial-Audio20 | N/A | 98 Kbps |
WebRTC-Tutorial-Audio40 | N/A | 98 Kbps |
Birds | 192×96 | N/A Kbps |
Note:
Please note that all video files used are uncompressed Y4M files. What testRTC will do over the network with these video sources is up to your application logic, network conditions and the machine performance, as these media sources get encoded by WebRTC in realtime.
Network Profile options
Choose one of the following values from the ‘Profile’ column and add it to your script as can be seen in the example above – “network”: “No throttling”
Profile | Bandwidth | Latency | Packet loss |
No throttling | No limitation | 0 | 0% |
Call Drop | 50 Kbps | 500ms | 20% |
DSL | 8 Mbps | 40ms | 0.5% |
Very Bad Network | 1 Mbps | 500ms | 10% |
Wifi | 30 Mbps | 40ms | 0.2% |
Wifi High packet loss | 30 Mbps | 40ms | 5% |
Regular 2.5G | 150 Kbps | 200ms | 3% |
Regular 3G | 750 Kbps | 250ms | 1.5% |
Poor 3G | 400 Kbps | 350ms | 5% |
Regular 4G | 4 Mbps | 0 | 2% |
Poor 4G | 4 Mbps | 350ms | 5% |
Unstable 4G | 4 Mbps | 500ms | 10% |
High Latency 4G | 4 Mbps | 600ms | 0.2% |
High Packet Loss 4G | 4 Mbps | 5ms | 20% |
50% Packet Loss | 40 Mbps | 10ms | 50% |
Firewall Profile
Choose one of the following values from the ‘Firewall Profile’ column and add it to your script as can be seen in the example above – “firewall”: “FW_NO_FW”
Firewall Profile | Description |
No Firewall | All ports are open |
FW – HTTP and HTTPS Allowed | Only HTTP & HTTPS allowed |
FW – HTTPS Allowed | Only HTTPS allowed |
FW – Baseline | Only ports that are required for the agent operation are open. |
For a detailed list of available firewall configurations, please refer to What are the test profile configurations?