Proxy settings for the Desktop App can be configured by opening the Edit menu and clicking on Preferences
The Proxy Settings window shows the available options for configuration:
In the Proxy Settings window, you can specify which traffic should use your proxy settings:
- Mabl: only traffic from the Desktop App to mabl will use the proxy settings
- Test: only traffic from browser-based and API tests will use the proxy settings
- Both: both Desktop App traffic and test traffic will use the proxy settings
- None: all proxy settings will be ignored
Disabling proxy settings
Selecting “None” will disable the proxy settings for both the mabl API and the test traffic, but will keep the proxy configuration itself intact. This option is useful for testing so that you don’t have to keep retyping the proxy settings.
This option tells the desktop app where to look for the proxy configuration.
- Automatic: If set to “Automatic”, the operating system proxy settings will be automatically imported and used.
- Manual: If, for some reason, the traffic to the mabl API or to the system under test require different proxy settings than the rest of the system, this option can be set to “Manual” and the necessary proxy configuration can be input using the provided fields.
To confirm that the proxy configuration works as expected, click the Test button in the bottom right of the Proxy Settings window to open the Validate Proxy Settings window:
Click on "Verify app connectivity" to check your connection to mabl services. If the Desktop App is able to successfully communicate with the mabl APIs, it will display a message indicating that the Desktop App is able to connect to mabl services.
Enter a URL (typically a link to some part of the system under test) in the “URL to test” field, and click on "Verify test connectivity.” If the desktop app is able to successfully communicate with the URL, it will display a message indicating that the test connection was successful.
Validating test traffic
There may be cases where test traffic validation behaves different from the actual test. There are many different proxy implementations, and we are unfortunately not able to test them all.
In the event that validation fails, but you believe the proxy settings to be correct, we recommend running an actual test to confirm whether the failed validation is the result of incorrect proxy settings or is caused by a subtle different between how the validation traffic and test traffic interact with your particular proxy configuration.
If your network firewall blocks outgoing requests, you will need to add the following domains to your firewall allowlist. This will allow through Desktop App traffic.
*.mabl.com *.googleapis.com *.rollbar.com *.fullstory.com *.segment.io *.intercom.io
Updated 14 days ago