Merv · Version 3.0.3

|

|

Merv-Local dashboard showing test suite cards and live execution chart

What is Merv-Local?

Merv-Local turns your automated test runs into rich HTML and Realtime reports on your machine — no central server or login required. Connect Cucumber, TestNG, JUnit 5, Playwright, or other runners once; open index.html in a browser (via a local web server) to browse runs, live suite status, consolidated history, and important KPIs built from available local test suite snapshots.

Each run gets a timestamped folder under merv.report.folder. While tests execute, open live suite HTML that polls report data in place. When the run finishes, use the dashboard to compare builds, spot flaky tests, triage failures, and track pass rate and duration trends.

  • Cucumber
  • TestNG
  • JUnit 5
  • Playwright (JS)
Merv-Local KPI execution summary with charts and pass metrics

See your test data come alive

Real screenshots from a sample Merv-Local run — suite cards, consolidated views, and analytics in one dashboard. Open the sample report →

Merv-Local dashboard

Reports on disk, insights in the browser

Open {reportRoot}/index.html after a run (serve over HTTP — see Documentation). Three main views share one data source: every run’s json/merv-report.json.

Merv-Local Dashboard

Suite pages, KPI panels, consolidated tables, and the live execution chart — carousel shows real Merv-Local screenshots from a sample run.

  • Test Suites — run cards, pass/fail/skip donuts, tags, live execution chart
  • Consolidated Report — testcase, tag, and failure summaries across runs
  • KPIs — execution summary, performance, flaky detection, trend charts
  • Live suite report — watch cases and steps update while tests run

Test Suites view

The default dashboard lists every run folder as a card and shows a live execution chart at the top. Search filters cards by folder name, suite title, and tags.

Live execution chart

Merv provides a time series for pass (green) and fail (red) completions per minute across listed runs.

  • Presets: 1 hour, 6 hours, 1 day, 1 week, 2 weeks, 1 month, or custom from/to
  • Reflects cases finished per minute, not starts

Execution Suite Dashboard

One Execution Suite per run folder, built realtime in execution so no need to wait to finish your execution.

  • Title, folder path, Completed vs In progress badge
  • Total, pass, fail, skip counts and pass/fail/skip donut
  • Environment, release, sprint meta when present in JSON
  • Tag pills, last-modified time, View Cases (suite HTML)
Merv-Local test suites dashboard with chart and suite cards
Test Suites — live chart and run cards

Consolidated Report

Based on the local execution, Merv provides a consolidated report with different analysis and views.

Consolidated testcase summary with expandable rows
TestCase Summary — status history per testcase

TestCase Summary

  • Current status from the newest execution
  • Last five runs — compact status history
  • Last passed / last failed timestamps
  • Total pass / total fail over discovered history
  • Expandable rows for per-run breakdown

Tag / Group Based Summary

Groups cases by scenario tags (e.g. @smoke). Multi-tag scenarios appear under each tag.

Failure Summary

Current failures only — latest failure reason per testcase; rows drop when the test passes again.

KPIs — everything in the dashboard

Merv provides a set of KPIs to help you understand the execution and performance of your test suite.

Test execution summary

  • Cards: total cases, passed, failed, skipped, pass %
  • Doughnut chart — outcome mix for scoped builds
  • Stacked bar chart — pass vs fail per execution

Execution time & performance

  • Total suite execution time and average test case time
  • Suite duration P95 / P99
  • Suite duration by run; chart of slowest cases; slow test cases list

Flaky test detection

Tests that both passed and failed in scope: failed-run count, passed-run count, stability, and pass/fail flips.

Trend analysis (build-wise)

  • Pass % over time — per-build pass rate
  • Failures per build — failure counts per run
  • Execution time trend — duration across runs

Per-run suite reports

Who is it for?

QA engineers, developers, and release owners who want live progress, historical comparison, and actionable KPIs from local or CI test runs — without a reporting server.

Start reporting in minutes

Wire Merv into your Cucumber, TestNG, JUnit, or Playwright project and open beautiful HTML reports from your CI artifact folder.

Documentation Sample report