.CYuT_dZX_1uGpNi.svg){kind=small}
.Bf10y01t_PVSYK.svg){kind=small}
.Cghii_pL_Z1DYVxU.svg){kind=small}
.CbeacWq7_1cxFXE.svg){kind=small}
.D2k-3zqT_Z10D5qc.svg){kind=small}
.C_Hn_1GY_NRL3p.svg){kind=small}
- Each parallel test another Chrome process
- A growing suite more CPU and memory
- CI machines sized for the peak
Sessions are free — pay only for traffic
Cloud Browser for Testing
Run browser tests in remote Chromium without keeping Chrome running on your own servers. Connect your existing Playwright or Puppeteer tests and run them in Cloud Browser sessions.
- Run end-to-end and UI tests in remote Chromium
- Test complete user flows with Playwright or Puppeteer
- Run multiple browser tests in parallel
Testing
Run browser tests
in remote Chromium
Start a Floppydata Cloud Browser session, connect your existing test code, and run your tests in remote Chromium. Check navigation, forms, logins, page interactions, and multi-step user flows.
Why Use a Cloud Browser for Testing?
Running more browser tests usually means more Chrome processes competing for CPU and memory. With a cloud browser for testing, Chromium runs remotely while your tests still control what happens in the browser.
This works well for end-to-end testing, regression checks, UI tests, and recurring test suites.
Test Complete User Flows in a Real Browser
Some problems only show up when someone actually starts using the page. A successful HTTP response doesn't tell you whether a form works, a button opens the right screen, or a login flow reaches the dashboard. Cloud Browser loads the full page in Chromium, including JavaScript and dynamic content. You can test:
-
Page navigation and redirects
-
Signup and login flows
-
Form filling and submission
-
Buttons, menus, and other UI elements
-
Multi-step user journeys
-
Dynamic content and JavaScript rendering
End-to-End Testing
Use Playwright or Puppeteer to run a complete user journey and verify each step along the way. Tests can cover anything from a signup form to a longer workflow across several pages.
Regression Testing
A code change can break a browser flow that worked in the previous release. Run the same tests in Cloud Browser after each update to make sure important pages and user journeys still work as expected.
Saved browser settings and state can also be reused across sessions when your tests need the same browser setup.
UI and Functional Testing
Some issues only appear when you actually interact with the page. Browser tests can click buttons, enter data, wait for dynamic elements, follow navigation, and check what happens after each action. This can catch problems that an API test or a basic HTTP check might miss.
Connect Playwright or Puppeteer over CDP
Floppydata Cloud Browser connects to Playwright and Puppeteer over the Chrome DevTools Protocol. You can keep using your existing test code to navigate pages, click elements, fill in forms, wait for content, and run JavaScript.
Your specs, our Chromium
You can use Playwright or Puppeteer from Python or Node.js. The assertions, fixtures and reporters you already have stay where they are.
Only the line that launches a browser changes — everything after it is the test you already wrote.
import { test, expect } from '@playwright/test';import { chromium } from 'playwright';test('checkout completes', async () => { const browser = await chromium.connectOverCDP(connectUrl); const page = browser.contexts()[0].pages()[0]; await page.goto(APP + '/checkout'); await page.click('#pay'); await expect(page.locator('.receipt')).toBeVisible();});import puppeteer from 'puppeteer-core';const browser = await puppeteer.connect({ browserWSEndpoint: connectUrl });const page = (await browser.pages())[0];await page.goto(APP + '/checkout');await page.click('#pay');await page.waitForSelector('.receipt');from playwright.sync_api import sync_playwright, expectwith sync_playwright() as p: browser = p.chromium.connect_over_cdp(connect_url) page = browser.contexts[0].pages[0] page.goto(APP + '/checkout') page.click('#pay') expect(page.locator('.receipt')).to_be_visible()A normal spec — only the browser it runs against changed.
Run Browser Tests in Parallel
Running a few browser tests locally is simple. As the test suite grows, Chrome starts using more CPU and memory. Cloud Browser lets you run tests across separate Chromium sessions. Floppydata supports up to 100 simultaneous browser sessions per account.
Run regression tests or multiple user flows in parallel instead of waiting for them to finish one by one.
Test Websites from Different Locations
Websites can behave differently depending on where the traffic comes from. Regional pages, redirects, localized content, APIs, and third-party resources may all vary by location.
Cloud Browser sessions run exclusively through Floppydata rotating proxies, so you can run the same tests from different proxy locations.
There is no runtime or per-session fee for Cloud Browser. You only pay for the Floppydata proxy traffic your sessions use.