Unified dashboard
Every run as a suite card — pass, fail, skip counts, tags, environment meta, and live in-progress badges.
Merv-Local 4.0.0 · Merv-Server
|
|
Why teams use MERV
- Centralized realtime test reporting
- Local HTML → Cloud dashboard
What is MERV?
MERV (Metrics Engine for Reports & Visualization) is centralized realtime test reporting
for automation — one place to see every suite, testcase, step, screenshot, and KPI instead of scattered logs and
one-off HTML files. Whether reports stay on disk (Merv-Local) or sync to the cloud
(Merv-Server), the same merv-client integration gives your team a
single reporting model.
Connect Cucumber, TestNG, JUnit 5, Playwright, or Cucumber-js once. Browse runs on a live dashboard, compare history in a consolidated view, triage failures, track pass rate and duration trends, and spot flaky tests — from your laptop or CI, local or server.
Live execution chart
Time-series of pass/fail completions across runs while tests execute — no waiting for the job to finish.
Consolidated history
Testcase status across all runs: last five results, last passed/failed, tag groups, and current failure summary.
KPI analytics
Pass %, doughnut and stacked bar charts, suite duration P95/P99, slowest cases, and build-wise trend lines.
Flaky test detection
Tests that both pass and fail in scope — stability score, flip counts, and failed-run history.
Step detail & screenshots
Per-step status, expected/actual, error messages, viewport PNGs, and plugin rows (data, validation, info).
Tag-based analysis
Filter and summarize by @smoke, @regression, browser tags, and custom scenario tags.
Local or cloud
Same merv.properties toggle: rich HTML on disk, or push suites to merv.online/app for the team.
Report support
See centralized reporting in action
Real screenshots from a sample Merv-Local run — the same views you get on disk or after ZIP import on Merv-Server. Open the sample report →
Merv-Local
Merv-Local is centralized reporting on your machine —
no account or server required. Connect your test framework via merv-client; each run writes JSON and
HTML under merv.report.folder. Open index.html through a local web server to browse
every run, live suite status, consolidated history, and KPIs.
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 export
merv-report-upload.zip for Merv-Server import.
Merv-Server
Merv-Server is centralized reporting in the cloud: create an account,
set up workspace and projects, add merv.properties with merv.local=false, and your automation
sends suites, cases, and steps to MERV — no merv-reports/ folder on every machine.
Account → workspace → Hierarchy ID → API key → run tests. Results appear at
https://merv.online/app for your team — share a link instead of zipping local HTML.
- REST API
- Web dashboard
- API keys
- ZIP import
- Multi-project
Merv-Server
Test suites · cases · steps · KPIs
- Personal & team workspaces
- Share reports with a link — no local folders
- Real-time suite updates from CI
- Custom KPIs and project views
- Merge suites across pipelines
Compare Merv-Local & Merv-Server
Two ways to report — same merv-client
Merv-Local writes json/merv-report.json and HTML under
merv.report.folder. Merv-Server stores suites in MySQL and shows them in the
Merv App. Toggle with merv.local in merv.properties.
Merv-Server
Central API + web UI: projects, test suites, testcase management, dashboard KPIs, API keys,
and upload of merv-report-upload.zip from local runs.
- Account — register, verify email, sign in at
https://merv.online/app - Workspace — personal or organization; projects & SubProjects
- Hierarchy ID — copy from project card →
merv.parent_hierarchy - API key — Account Settings; paste into
merv.properties
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)
Consolidated Report
Based on the local execution, Merv provides a consolidated report with different analysis and views.
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
merv-report-live.html— live suite while tests runmerv-report.html— final suite with steps and screenshots- Step screenshots — click a step header in the suite report to show/hide captured images (JUnit, TestNG, Cucumber)
- Plugin steps — data, validation, and info rows via
MervReporter
Who is it for?
QA engineers, developers, and release owners who want centralized visibility into test runs — live progress, historical comparison, and actionable KPIs — on disk with Merv-Local or in the cloud with Merv-Server.
Start reporting in minutes
Choose Merv-Local for on-disk HTML, or Merv-Server to send reports to the cloud — account, API key, and merv.local=false.