Why most Playwright setups fail
Why bad Playwright setups cost more than bad tests, and how to build good ones
by Oliver Stenbom
Launch hundreds of browsers
Test critical user flows
Expect results in seconds
Endform lets you ship code frequently and confidently by running your Playwright end-to-end tests 10x faster.
app.com
E2E Test Running
app.com
E2E Test Running
app.com
E2E Test Running
app.com
E2E Test Running
app.com
E2E Test Running
app.com
E2E Test Running
app.com
E2E Test Running
app.com
E2E Test Running
app.com
E2E Test Running
app.com
E2E Test Running
0started browsers
|
0completed tests
Trusted by the fastest growing companies out there
(Un)paralleled
performance
Run all of your Playwright end-to-end tests at the same time.
Welcome to a world where your suite speed is bottlenecked by the
slowest test.
$ |
Running 0 tests in parallel
Come as you are
Bring your Playwright suite as it is - no jumping through hoops.
Global set up, Playwright projects, custom dependencies?
We support your favourite Playwright features.
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});
Keep it green
Powerful analytics of your tests over time.
Straightforward flaky test and error identification using historical
data.
Pay for what
you use
Only pay for test runtime - we bill by minutes of used
infrastructure.
Reduce your bill by improving your tests.
From the blog
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.