Introducing Euriqa: The Test Automation Platform Built for Playwright

The Problem with Playwright Reporting Today

If you run Playwright tests in CI, you already know the pain. A test fails on the main branch. You get a Slack notification — or worse, you find out when someone else's merge breaks. Now the debugging ritual begins.

First, you open the CI job. You scroll through hundreds of lines of terminal output looking for the failure. You find it, but the error message is truncated. Or it says something useless like locator.click: Target closed. You need more context.

So you download the HTML report artifact. You unzip it. You open it locally. You find the failing test, look at the screenshot, maybe open the trace viewer. You start to get a picture — but this took ten minutes, and you still don't know if this test has failed before.

Now multiply that by ten engineers and five hundred tests. Every day.

The default Playwright HTML reporter generates local files that cannot be shared with your team. There is no historical view. No flakiness tracking. No way to know if a failure is new or has been happening intermittently for two weeks. Teams end up tracking flaky tests in spreadsheets, pinging each other on Slack to ask "is this test known-flaky?", and wasting hours on failures that turn out to be infrastructure noise.

This is the status quo for most Playwright teams, and it does not scale.

Why We Built Euriqa

We built Euriqa because we lived this pain ourselves. We ran large Playwright suites in CI across multiple services, and we were tired of the same cycle: test fails, dig through CI logs, download the HTML report, try to reproduce locally, realize it was flaky, add it to the spreadsheet, move on. Repeat tomorrow.

We wanted a single place where the entire team could see every test run, drill into any failure, access screenshots and traces without downloading zip files, and know instantly whether a failing test was a real regression or a known flaky issue.

Nothing on the market did this well for Playwright. Generic test reporting tools treat Playwright as an afterthought. They don't understand steps, fixtures, hooks, retries, sharding, or traces. They give you charts, but not the context you need to actually fix failures.

So we built the test automation platform we wished we had — purpose-built for Playwright from the ground up, with intelligent reporting, orchestration, AI-powered debugging, and expert services.

What Euriqa Does

Centralized Dashboard

Every test run appears in the Euriqa dashboard with full context: branch, commit, CI provider, pass rate, duration, and test counts. You can filter by status, branch, or date range. Click into any run to see the full test list, organized by file and suite.

No more digging through CI logs. No more asking teammates "did the tests pass on main?" Open the dashboard and you know.

Real-Time Streaming

With real-time streaming enabled, you see test results as they execute — not after the entire CI job finishes. For teams running long suites (30 minutes, an hour, or more), this is critical. You can catch a critical failure five minutes into a run instead of waiting for the whole thing to complete.

Flakiness Intelligence

Every test in your suite gets a flakiness score between 0 and 1, calculated from its historical pass/fail pattern. A score of 0 means the test is perfectly stable. A score above 0.3 means it needs attention.

Euriqa tracks flakiness trends over time, so you can see whether your suite is getting more or less stable. When a test crosses a configurable threshold, Euriqa can automatically quarantine it — flagging it in the dashboard so your team knows it is being managed, without manually maintaining a spreadsheet of known-flaky tests.

This changes how teams deal with flakiness. Instead of reactive fire-fighting, you get a system that surfaces the worst offenders and tracks your progress in fixing them.

Full Artifact Access

Screenshots, videos, and Playwright traces are uploaded automatically and viewable directly in the browser. Click on a failing test and see the screenshot of the failure state. Open the trace to step through every action, network request, and DOM snapshot.

Everything is served through secure signed URLs. No downloading zip files from CI artifacts. No asking a teammate to send you their local report. The full debugging context is available to everyone on the team, instantly.

Analytics and Optimization

Euriqa does not just show you data — it tells you what to do with it.

Duration trends show you how your suite's execution time changes over time, so you can catch regressions before they slow down your pipeline. Retry analysis quantifies exactly how much CI time is wasted on retries, broken down by test. The slowest tests view ranks tests by execution time so you know where to focus optimization efforts.

And the optimization recommendations engine gives you concrete, actionable suggestions: which tests to parallelize, which retry configurations to adjust, which slow tests would benefit from refactoring. Not just charts — recommendations you can act on today.

How It Works

Getting started with Euriqa takes less than five minutes. There are three steps, and none of them require changing your test code.

Step 1: Install the reporter.

npm install @euriqa/euriqa-playwright

Step 2: Add it to your Playwright config.

// playwright.config.ts
import { defineConfig } from '@playwright/test'

export default defineConfig({
  reporter: [
    [
      '@euriqa/euriqa-playwright',
      {
        apiKey: process.env.EURIQA_API_KEY,
        projectId: process.env.EURIQA_PROJECT_ID,
      },
    ],
    // Keep your existing reporters too
    ['html'],
  ],
})

Step 3: Set two environment variables and run your tests.

export EURIQA_API_KEY=your-api-key
export EURIQA_PROJECT_ID=your-project-id

npx playwright test

That is it. Your test results, screenshots, videos, and traces flow to the Euriqa dashboard automatically. Zero changes to your test files. The reporter hooks into Playwright's built-in reporter API, so it works alongside your existing reporters — you can keep the HTML reporter, the list reporter, or whatever you use today.

What You Get on Day One

After your very first test run, you have a fully populated dashboard. You can see pass rates across your suite, drill into individual test results with step-level detail, view screenshots and traces in the browser, and get a baseline flakiness score for every test.

There is no "wait two weeks for enough data" period. The dashboard is useful from run one, and it gets more powerful with every subsequent run as Euriqa builds historical trends and refines flakiness scores.

A Platform Built for Playwright, Not Adapted for It

Euriqa is not a generic test reporting tool that bolted on Playwright support. It is a test automation platform built from the ground up for the Playwright ecosystem. That means native support for everything Playwright exposes through its reporter API:

• Steps and actions — Every click, fill, goto, and assertion captured with timing
• Fixtures and hooks — beforeEach, afterEach, fixture setup and teardown tracked as first-class steps
• Retries — Full retry tracking with per-attempt results, so you can distinguish real failures from flaky retries
• Sharding — Shard-aware reporting that reconstructs the full picture even when your suite runs across multiple machines
• Traces — Playwright trace files viewable directly in the dashboard, no download required
• Parallel workers — Worker and parallel index tracking for understanding execution distribution
• Projects — Multi-browser and multi-config project support, so you can see results for Chromium, Firefox, and WebKit side by side

If Playwright captures it, Euriqa captures it.

What's Coming Next

Euriqa is just getting started. Here is what is on our roadmap as we expand the platform:

AI-powered debugging — Click "Debug with AI" on any failing test and get an instant root cause analysis. The AI examines the error, stack trace, test steps, and screenshots to tell you what went wrong and suggest a fix. No more manually correlating error messages with screenshots and traces.

Predictive flakiness — Identify tests that are likely to become flaky before they start failing, based on execution pattern analysis. Fix instability proactively instead of reactively.

Failure clustering — Automatically group related failures together, even when error messages differ. When a shared dependency breaks, you see one cluster instead of fifty individual failures.

Slack and Teams notifications — Native integrations that post rich test summaries to your team channels. Know about failures the moment they happen, with direct links to the Euriqa dashboard.

PR status checks — Block pull request merges based on test results and flakiness thresholds. Make test quality a first-class gate in your development workflow.

Get Started

Euriqa's free Hobby plan includes unlimited test runs, 3 admin/member seats, unlimited viewer seats, 7 days of data retention, and basic test orchestration. No credit card required. Sign up, install the reporter, and have full visibility into your Playwright tests in under five minutes.

Your team deserves better than CI logs and local HTML files. Get started free at app.euriqa.dev.