Testing

Test the journey.On real hardware.

Validate browser flows on consumer desktop hardware and physical mobile devices. Bring Playwright or Puppeteer, exercise current browsers with native GPU rendering, and see the full session when a test needs investigation.

  • Playwright & Puppeteer
  • GPU in every instance
  • Physical mobile devices
Your workflow, connectedTesting
  1. 01Your test suite
  2. 02Desktop or physical mobile
  3. 03GPU-backed real browser
  4. 04Live view, logs + recording
Exercise → assert → investigateYour suite owns the assertions. The platform provides the browser and session evidence.

Built for Testing

Test more than a resized viewport.

Choose a real device environment for the flows you care about, then use your test code to check behavior and results.

01

End-to-end web journeys

Exercise sign-in, navigation, forms, and checkout flows in the applications you test. Connect from your existing test runner and keep assertions in your suite.

02

Physical mobile validation

Check mobile web layouts and interactions on physical mobile devices. Test the actual device environment alongside your desktop coverage.

03

Graphics and location-sensitive pages

Exercise WebGL, canvas, and visual interfaces with a native GPU. Use proxy targeting to investigate pages that vary by geographic location.

The Cloud Dev Tools difference

Real hardware.
Every browser layer covered.

Browser access is more than an endpoint. These capabilities work together underneath your code, across AI agents, scraping, automation, and testing.

01 / Automation

A firewall for Puppeteer and Playwright

Automation libraries can leak objects that a website’s web application firewall detects. Our own firewall sits between libraries such as Puppeteer and Playwright and the browser to prevent those detectable object leaks.

Your library → CDT firewall → Browser

02 / Graphics

A GPU in every instance

Every browser instance has a native GPU for hardware rendering. WebGL, canvas, video, and page composition use real graphics hardware, with actual consumer CPU and RAM values reported in JavaScript.

Consumer CPU · Real RAM · Native GPU

03 / Devices

Physical mobile devices

Run desktop browsers on consumer hardware or choose physical mobile devices. Mobile sessions use an actual mobile browser environment rather than desktop emulation with a smaller viewport.

Real desktop hardware · Physical mobile

04 / Network

The right route for the destination

Choose datacenter, residential, or mobile proxies, city-level targeting, or bring your own proxy. The API’s domain-based routing keyword helps automatically select an appropriate proxy for your target website.

Domain-based routing · Flexible proxies

05 / Browser

Current browsers. Native handshakes.

We run regular browsers and keep them up to date. TLS and protocol handshake parameters come from the browser itself, without tying your workflow to an older browser binary bundled with an automation library.

Up-to-date browsers · Native protocols

06 / Interaction

Input through the human path

Mouse and keyboard events execute at the system level, through the same input path as real peripherals. Movements and keystrokes mimic human behavior instead of relying only on synthetic page events.

System-level mouse · System-level keyboard

From code to browser

Keep the familiar.
Connect to something better.

Use Playwright or Puppeteer with a managed browser endpoint. Start with the connection details in the API documentation.

Read the integration documentation
  1. 01

    Select the environment

    Choose the desktop or physical mobile profile for your test. Every instance includes a GPU for native graphics rendering.

  2. 02

    Connect your test code

    Point your Playwright or Puppeteer browser connection at Cloud Dev Tools. Keep the runner, assertions, and CI orchestration in your project.

  3. 03

    Inspect failures in context

    Follow the live view or return to the session history for logs and recordings. Use the portal to try supported-language test code without local setup.

From development to investigation

See the run.
Understand the result.

The browser is only half the workflow. Develop in the portal, follow active sessions, and return to the evidence when something needs a closer look.

Cloud Dev Tools session history with searchable logs, browser recordings, proxy details, and CAPTCHA solver status
Session history, network details, and recordings in one view.

Live session views

Let people and AI agents follow the browser as a workflow runs.

Searchable logs and replay

Find past sessions, inspect detailed logs, and review clear recordings.

A portal for development

Write and run tests in supported languages without local IDE or environment setup.

Locally run AI CAPTCHA assistance

Use local AI models to help resolve difficult CAPTCHA challenges during a session.

Common questions

Testing,
explained.

Are the mobile devices emulators?

No. Mobile profiles run on physical mobile devices rather than desktop browser emulation. Desktop browsers run on real consumer hardware.

Can I connect from my existing CI pipeline?

Your CI job can use a Playwright or Puppeteer client to connect to the remote browser endpoint. Keep test execution, assertions, and reporting in your existing pipeline.

Is this a replacement for my test framework?

Cloud Dev Tools provides the browser environment and session visibility. You continue to use your own test framework and assertions. Validate framework and device compatibility for your suite.

A complete browser foundation

Bring real hardware into your test workflow.