QA testing

Test public web flows through an approved region

QA needs to check how public web flows behave from an approved region, with clear limits and a record of who ran the session.

Request access See region controls

Real-world situation

A QA team validates checkout, signup and localization flows from an approved egress region before a release. The product owner needs repeatable testing and a session trail, while security wants the use case bounded to public web flows and named testers.

What buyers worry about

Regional testing must not look like anonymous browsing, scraping or block evasion.
The team needs to know which tester ran which session and which limits applied.
Private and internal ranges must stay out of the browser-proxy path for this scenario.

What you control

Control allowed egress region, routing mode, work domains, traffic limits, domain/category policy, active sessions, and session history.

What stays outside

This is for accountable testing of public web experiences. It is not for unblocking, scraping, anonymity, bypassing restrictions, or testing private/internal networks through the browser-proxy path.

Review

What administrators can verify

Tests run only through regions allowed by the current plan and policy.
Session history shows who connected, when the run happened and which limits applied.
Traffic and session limits keep each run bounded.
HTTPS page content is not decrypted on the managed browser path.
Private and internal network ranges stay blocked on the browser path.

Success signals

QA can repeat the same public flow from the approved region with named-user session history.
Traffic and session limits make the test window bounded and reviewable.
The policy makes clear that this is controlled testing, not automated collection or evasion.

Rollout

What the workflow looks like

Create a QA workspace or group with the approved region and allowed public test domains.
Set traffic and session limits that match the planned release test window.
Have testers sign in, run the browser flow and record the session identifiers in the test evidence.
Review session history after the run and close the QA access window.

FAQ

Can we use this for scraping or bypassing restrictions?

No. BusinessProxy is for accountable work browsing and public web testing. It is not an anonymity, scraping, unblocking, or evasion tool.

Can QA choose any country?

Only approved egress regions exposed by the current plan are shown. Global region coverage is available only where the region catalog and plan support it.

Does this inspect test page content?

Not on the browser-proxy path. HTTPS page content is not decrypted; policy is enforced through domains, metadata, configured rules, and category data.

Related use cases