Playwright sends its results to Probara

Manage Playwright test automation in Probara

Add the Probara reporter to playwright.config and every CI run becomes a Probara test run, with each attempt’s steps, errors and attachments, linked to its test case.

Start freeSee documentation

Integrations are included in the Pro plan, and in the 14-day Pro trial every new organization starts with. Compare plans

Every CI run becomes a Probara run

The reporter runs inside the same npx playwright test command, next to the reporter you read in the terminal. There is no separate upload step, and the run is closed once every result is in.

It signs in with an organization app token read from the environment: it uses no seat and keeps working when the person who created it leaves.

GitHub Actions
- name: Run Playwright tests
  run: npx playwright test
  env:
    PROBARA_API_TOKEN: ${{ secrets.PROBARA_API_TOKEN }}

Every attempt, with its steps and evidence

Probara records one result per attempt, so a retried test keeps every attempt in its history while the run case shows the last outcome.

Each attempt carries the steps it ran with their status, duration and error, the parameters it ran with, and its screenshots, videos and traces.

The first, failed attempt of a retried Playwright test: its screenshots and its steps, with the timeout error of the 3-D Secure challenge

See the trace without downloading it

Open the trace of any attempt with one click, right from its result, and replay every step of the test in your browser. No downloading files, no separate tools.

It works as soon as your tests report to Probara: there is nothing else to set up.

The Playwright Trace Viewer served by Probara, open on a sign-in test

Tests link to their cases, and missing cases are created

Name a case with a probara_case annotation, an ID in the test title, or probara.id() at run time, and the result goes to that case.

A test that names none is matched by its automation key. The first time it reports, its case is created under a suite path built from its file and describe blocks.

tests/checkout.spec.ts
test(
  'pays with a card',
  { annotation: { type: 'probara_case', description: 'SHOP-12' } },
  async ({ page }) => {
    // ...
  },
);

One run for a sharded pipeline

Merge the blob reports of every shard with the reporter, and the whole pipeline lands as one Probara run, with the same keys as one run of the whole suite.

If results should appear while the shards run, create the run first and report into it from each shard. Parallel workers of one playwright test need nothing.

Terminal
# Each shard writes its blob report
npx playwright test --shard=1/4

# One job merges them into a Probara run
npx playwright merge-reports --reporter @probara/playwright-reporter ./all-blob-reports

Other integrations

All integrations

Send your first Playwright run to Probara

Create your organization, create an app token and add the reporter. Every new organization starts on a 14-day Pro trial, with no credit card.

Start freeSee documentation