Proxy & Remote Browser Profiles

Configure reusable proxy and remote browser profiles in ContextQA, assign them to test cases or plans, and keep connection secrets protected.

Quick answer

Create organization-level connection profiles under Settings → Organization Setting → Proxy or Remote Browser, then select a profile in a test case or test plan. A proxy routes execution through an internal network; a remote browser sends execution to an external WebSocket browser endpoint. Remote browser profiles must pass Test Connection before they can be saved.

What this page covers

Who is this for? Administrators and SDETs who need ContextQA to reach private applications, route traffic through an approved network, or execute against a managed browser grid.

Organization profile library

Organization settings with Proxy Profiles and Remote Browser Profiles

Profiles are reusable at organization scope. Create them once, then assign them from the test case or test plan that needs the connection.

Profile	Required fields	Optional fields	Typical use
Proxy	Name, Proxy URL such as http://host:port	Username, password	Reach an application through a corporate proxy or approved egress path.
Remote Browser	Name, Remote Browser URL such as wss://host:port	Username, password	Run against an external browser endpoint or browser grid.

Use a dedicated automation credential with the minimum access required. Do not paste credentials into test-step text, test names, screenshots, or documentation.

Add a proxy profile

1

Open the Proxy section

Go to Settings → Organization Setting, then select Proxy.

2

Enter the connection

Select Add Proxy. Enter a recognizable name and a proxy URL in http://host:port form. Add the username and password only when the proxy requires authentication.

3

Save the profile

Select Add Proxy. The profile becomes available in test-case and test-plan settings.

Add a remote browser profile

1

Open the Remote Browser section

Go to Settings → Organization Setting, then select Remote Browser.

2

Enter the endpoint

Select Add Remote Browser. Enter a recognizable name and the WebSocket endpoint, normally in wss://host:port form. Add credentials only when the endpoint requires them.

3

Test the connection

Select Test Connection. ContextQA enables saving only after the current URL and credentials pass the connection test. If you change the URL, username, or password after a successful test, test the connection again.

4

Save the profile

Save the profile after the successful connection result appears.

Assign a profile

Choose the connection at the narrowest useful scope:

• Use the test plan setting when every mapped suite should use the same route or remote grid.
• Use the test case setting for a targeted exception.
• Select None when the case or plan should not use a saved profile.
• Requirement imports that create a plan can also expose proxy and remote-browser selections in their advanced configuration.

After assigning a profile, run a non-destructive smoke test before adding the profile to a broad regression plan.

Secret-handling behavior

When you edit a saved profile, the password field opens blank. The stored secret is not loaded back into the browser.

• Leave the field untouched to keep the current credential.
• Enter a new value to replace it.
• If your organization rotates a password, retest the remote browser connection before saving.

This behavior reduces the chance of exposing a reusable credential in the portal or a screenshot.

Troubleshooting

Save is disabled for a remote browser profile

Select Test Connection. Saving remains disabled until the current endpoint and credential values pass.

The profile does not appear in a test case or plan

Confirm that the profile was saved in the same organization, refresh the selector, and clear any search text. Profile lists are organization-specific.

The connection works locally but the ContextQA run cannot reach it

Confirm that the endpoint is reachable from the ContextQA execution environment, that the scheme and port are correct, and that network allowlists include the approved ContextQA execution source for your deployment.

Related documentation

• Test plans
• Create test cases
• Environments
• System configuration

Need to test a private application or managed browser grid? Book a Demo → — See how ContextQA fits your network and execution architecture.