How Lovable 10x'd their Playwright test suite while speeding up CI
Lovable moved their Playwright test suite to Endform, increased their coverage by 10x while reducing execution time by 80% — now running 400k+ tests per week.
Read the storyFocus on quality
Run Playwright tests at scale with Endform
Up to 10x faster suites by changing a single CLI command
12 browsers testing
Trusted by the fastest growing companies out there
Use what you already have
Work with your existing Playwright setup
Endform reads your existing playwright.config.ts, including Playwright projects and global setup. Keep custom dependencies, local services, and reporters in place.
Switch one CLI command to run the same suite on Endform, without rewriting tests or maintaining a second configuration.
1import { defineConfig, devices} from ;
2
3if (!process.) {
4 throw new Error("PREVIEW_URL must be set");
5}
6
7export default defineConfig({
8 testDir: "./tests",
9 fullyParallel: true,
10 forbidOnly: !!process.env.CI,
11
12 reporter: [["list"], []],
13 use: {
14 baseURL: process.env.PREVIEW_URL,
15
16
17 },
18
19
20 command: "npm run dev",
21 port: 3000,
22 },
23
24
25 globalTeardown: require.resolve("./global-teardown"),
26
27
28 {
29 name: "setup",
30 testMatch: "setup.spec.ts",
31 },
32 {
33 name: "chromium",
34 testIgnore: "setup.spec.ts",
35 dependencies: ["setup"],
36 use: {
37 ...devices["Desktop Chrome"],
38 },
39 },
40 ],
41});
1import { test, expect } from '@playwright/test';
2import { helperFunction, type HelperPage } from ;
3import { generateEmail } from ;
4
5test.describe('Dashboard', () => {
6 test('should display user dashboard correctly', async ({ page }) => {
7 await page.goto('/dashboard');
8
9 // Check page title
10 await expect(page).toHaveTitle(/Dashboard/);
11
12 // Verify navigation elements
13 await expect(page.getByRole('navigation')).toBeVisible();
14 await expect(page.getByTestId('user-menu')).toBeVisible();
15
16 // Check main content areas
17 await expect(page.getByTestId('stats-grid')).toBeVisible();
18 await expect(page.getByTestId('recent-activity')).toBeVisible();
19 });
20});
Infinite scalability
Playwright parallel testing in seconds
Endform runs each test on its own isolated machine, in parallel. There is no sharding plan to tune as the suite grows.
Instead of being limited by your sharding setup, your suite finishes as soon as the slowest test is done.
$ |
Running 0 tests in parallel
A faster inner loop
Leverage suite context to write and update tests
Endform gives you and your agents the full context of your suite: live browsers from running tests, historical failure reasons, and rich results.
Reach testing confidence sooner with best-in-class writing, debugging, and querying tools.
Endform test context
- 01Start from your existing tests
Reuse your setup projects and fixtures to write and debug tests that already exist.
auth.setup.tsfixtures.ts - 02Query failure history
Why has checkout.spec.ts failed before?4 related runs / recurring network timeout
- 03Understand the resultBackend-linked OTel traceFull Playwright traceScreenshots
Outer loop maintenance
Keep your test suite green with flaky test detection
Endform builds a historical view of test health across runs, so inconsistent failures stand out from one-off errors.
See which tests needed retries, inspect recurring errors, and open available traces to understand what happened before flakiness slows the team down.
Customer stories
Quality infrastructure for teams moving fast
Why Matsmart switched from Checkly to Endform
Matsmart moved from Checkly to Endform to get full Playwright support and flexible parallel execution.
Read the story
How Vitalize Care cut their test suite from 15 minutes to 5 minutes
Vitalize Care reduced their Playwright test suite runtime by 3x with Endform, enabling faster iteration on their AI-powered nurse scheduling platform.
Read the storyPay for what
you use
Get started with 2,000 free test minutes, then pay $0.01 per test minute.
Reduce your bill by improving your tests.
From the blog
Introducing Playwright OpenTelemetry: Trace your tests across the entire stack
Without backend context, a failing Playwright test leaves you guessing. This open-source reporter and fixture propagates W3C trace context into your stack.
by Oliver Stenbom
Playwright on Vercel with Endform: the dream end-to-end testing setup
Announcing the Endform Vercel integration - the best way to end-to-end test for the web
by Oliver Stenbom
Playwright on GitHub Actions: The setup that actually runs fast
Playwright CI should not crawl. Learn how to cache browsers, run tests in parallel, and cut GitHub Actions time fast.
by Jakob Norlin
Frequently Asked Questions
What is Endform?
Endform runs browser based end to end tests for web applications quickly and reliably. We target the end to end testing framework Playwright.
How do I get started with Endform?
Getting started with Endform is easy! Just switch out one CLI command and you are up and running. We are fully Playwright compatible - no configuration changes needed.
How does Endform work?
Endform distributes your Playwright tests across hundreds of machines in the cloud. We run one test per machine, and coordinate the collection of results. This way your test suite finishes in the fastest possible time, while letting you focus on writing tests instead of managing infrastructure.
How fast is Endform compared to other runners?
Endform runs Playwright tests significantly faster than traditional runners by utilizing full parallelization and a highly optimized runtime.
We have seen speedups of some test suites of over 20x, and we can run most test suites in under 2 minutes.
Do you support other test frameworks than Playwright?
No. As of today we only support running Playwright tests. This lets us focus on providing the best possible experience for Playwright users. In the future we may consider adding support for other frameworks.