Merv-Local 4.0.22 · Merv-Server

|

|

Why teams use MERV

  • Centralized realtime test reporting
  • Local HTML → Cloud dashboard
  • Centralized local log analysis
What is MERV? Sample report Go To App
Merv-Local dashboard showing test suite cards and live execution chart

What is MERV?

MERV (Metrics Engine for Reports & Visualization) is centralized realtime test reporting and logging visualization for development and automation teams — 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.

Unified dashboard

Every run as a suite card — pass, fail, skip counts, tags, environment meta, and live in-progress badges.

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.

Centralized local log analysis

Pull logs from Spring Boot, SLF4J, Log4j, Playwright, and other tools into one Merv-Logs view — filter by project, level, and suite on disk.

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.

Merv-Doctor — one-command setup

Scaffold or heal merv.properties, Maven dependency, and Spring Boot logback-spring.xml with merv-client doctor setup / setup-log.

Merv-Doctor — wire your loggers

Route System.out, SLF4J, Log4j, and console.* into Merv-Logs with doctor set console and MervLogAppender — idempotent, reversible with unset.

Merv-Tutor — step debugger

Run small JS/TS files with npx merv-tutor, then npx merv-tutor open to step line-by-line with source on one side and live variables on the other.

Merv-Tutor — teach & inspect

Multi-file project traces, console mirror, and complexity hints under merv-reports/merv-tutor/ — built for lessons and debugging, not suite noise.

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 →

Test suites view with execution chart

Test Suites

Run cards, donuts, tags, and a live execution chart

 Consolidated testcase summary table

Consolidated Report

History across every run folder on disk

 KPI dashboard with doughnut and bar charts

KPI analytics

Pass rates, performance, flaky detection

 Trend and performance KPI panels

Trend analysis

Build-wise pass % and duration trends

 Tag and group based summary

Tag summary

Group cases by @smoke, @regression, and more

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-Local documentation → Sample report

Merv-Local KPI execution summary with charts and pass metrics

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 guide → Create account

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

Merv-Doctor

Merv-Doctor is the setup and healing CLI built into merv-client. One command scaffolds or repairs MERV wiring in your project — without rewriting your existing settings.

Use it for Java/Maven and Spring Boot apps, or JS/TS packages: create merv.properties, add the dependency, wire Logback / console into Merv-Logs, and keep everything idempotent so re-running doctor is safe.

  • Faster onboarding — doctor setup / setup-log instead of hand-editing configs
  • Heals missing keys — appends only absent merv.* properties; never overwrites yours
  • Spring Boot ready — adds logback-spring.xml with MervLogbackAppender when detected
  • Logger bridge — doctor set console routes System.out, SLF4J, Log4j, and console.* into Merv-Logs
  • Reversible — doctor unset console removes doctor-managed wiring cleanly
  • Same CLI everywhere — ./merv-client doctor … (Java) or npx merv-client doctor … (JS)

Download merv-client → Doctor commands 

# Java / Maven / Spring Boot
./merv-client doctor setup
./merv-client doctor setup-log
./merv-client doctor set console

# JavaScript / TypeScript
npx merv-client doctor setup-log
npx merv-client doctor set console
npx merv-client doctor unset console

Merv-Tutor

Merv-Tutor is a line-by-line step debugger for small JavaScript and TypeScript files — built for teaching, learning, and inspecting runtime behavior without mixing noise into Playwright or Cucumber suite reports.

Run a script with npx merv-tutor, then open the debugger with npx merv-tutor open. You get source on one side, variables in scope on the other, plus mirrored console output — all under merv-reports/merv-tutor/.

  • Learn by stepping — walk assignments, loops, branches, and function calls one line at a time
  • See memory live — inspect variables in scope at every step (Next / Prev)
  • Multi-file lessons — keep several scripts in Project Files; re-run replaces only that file’s trace
  • Console + trace — terminal console.log still prints and is mirrored in the tutor UI
  • Tutor-only reports — no suite folders; dedicated merv-tutor.html and latest.json
  • TS ready — pass .ts directly; esbuild compile then Babel instrumentation

Merv-Tutor guide → Docs overview

Merv-Tutor debugger

Source · variables · console

  • Step Next / Prev through instrumented lines
  • Table of vars in memory at each step
  • Separate from suite HTML & Merv-Logs noise
  • npx merv-tutor lesson.js then open

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 on cloud 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
User guide Create account

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
Merv local HTML report preview
Sample report Documentation

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.

KPI execution summary with doughnut and stacked bar charts
Execution summary & stacked outcomes
KPI trend analysis charts
Trend analysis — pass %, failures, duration

Test execution summary

  • At-a-glance counts for total, passed, failed, skipped — plus overall pass rate
  • Outcome mix doughnut — see the share of pass / fail / skip across the builds in scope
  • Per-run stacked bars — compare pass vs fail for each execution side by side

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 centralized visibility into test runs — live progress, historical comparison, and actionable KPIs — on disk with Merv-Local or in the cloud with Merv-Server.

Our Team

MERV is built by the team at TechElliptica. Connect with us on LinkedIn.

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.

Merv-Local docs Merv-Server guide Sample report