[ TEST ANALYTICS FOR PLAYWRIGHT + CYPRESS ]

Ask anything about your test runs.

Every run, its logs and your own properties, queryable by you or your coding agent over MCP.

QUERY

› Which checkout tests got slower after we moved CI to Node 22?

RESULT · EXAMPLE DATA

testnode 20node 22
saved card4.1s7.9s
coupon2.6s3.8s
guest5.0s5.2s

HOW IT WORKS

Three steps from test run to answer.

01 / REPORTER

Add the reporter

One API key. Results, steps, timings, retries, logs and environment details are collected for you.

// playwright.config.ts
reporter: [
  ['@testlore/playwright', {
    apiKey: process.env.TESTLORE_KEY,
  }],
],

02 / PROPERTIES

Tag what matters to you

Attach your own properties and events to a run, suite or test. They become queryable straight away.

testlore.set({
  tenant: 'acme',
  paymentProvider: 'stripe',
});
testlore.event('cart_ready');

03 / MCP

Ask from your agent

Connect the MCP server to Claude Code, Codex or Cursor and ask in plain English.

claude mcp add testlore \
  -- npx @testlore/mcp

› Is main ready to release?

FEATURES

Built for questions you haven't thought of yet.

01

A schema that is ready on day one

Runs, suites, tests and executions out of the box. Add your own fields without migrations.

02

Reporters for Playwright and Cypress

Drop-in reporters that need only an API key. No changes to how you write tests.

03

An MCP server your agent can query

Typed tools for filtering, grouping and comparing runs, so answers come from data, not guesses.

04

Custom events and properties

Track tenants, feature flags, build IDs or anything else, the way product analytics tracks users.

05

Searchable test logs

Console output, network errors and step logs are stored and searchable alongside every result.

06

A skill that instruments for you

When a question needs data you don't capture yet, your agent proposes the properties to add to your tests.

ASK ANYTHING

Questions teams ask Testlore.

Release readiness is one of them. The rest are whatever your team needs to know this week.

  • Which tests became flaky this sprint, and what changed in their environment?
  • Do failures cluster on one tenant, browser or feature flag?
  • How long has this timeout error been showing up in the logs?
  • Which suites cost us the most CI minutes last month?
  • Is this branch ready to release?

[ EARLY ACCESS ]

Get early access to Testlore.

We're onboarding Playwright and Cypress teams in small batches.