Coverage & Reporting

Maeris MCP provides detailed coverage analysis and report generation for UI tests, API testing, and security scanning. Coverage tools help you identify gaps — pages without tests, endpoints without assertions — so you can prioritize what to build next.

UI Coverage

The UI coverage command analyzes which pages, routes, and interactive components in your codebase have corresponding test cases:

maeris coverage ui

Example output:

UI Coverage Report
==================

Pages (8/12 covered — 67%)
  [✓] /login
  [✓] /register
  [✓] /dashboard
  [✓] /settings
  [✓] /users
  [ ] /billing          ← no tests
  [ ] /analytics        ← no tests
  [ ] /reports          ← no tests

Features
  [✓] Login form (3 tests)
  [✓] Registration flow (4 tests)
  [ ] Billing management (0 tests)
  [ ] Export functionality (0 tests)

Recommendation: Add tests for /billing, /analytics, /reports

Export UI coverage

maeris coverage ui --format json --output ui-coverage.json

API Coverage

API coverage compares the endpoints discovered by maeris scan api against those that have assertions defined in Maeris. Endpoints without assertions are flagged as uncovered:

maeris coverage api maeris coverage api --collection "My API Collection"

Example output:

API Coverage Report — My API Collection
=======================================

Total endpoints: 47
With assertions: 31 (66%)
Uncovered: 16 (34%)

Uncovered endpoints:
  DELETE /api/users/{id}
  PATCH  /api/users/{id}/status
  GET    /api/reports/export
  POST   /api/webhooks
  ...

Recommendation: Add assertions to 16 endpoints to reach 100% coverage

Test Results Reports

Generate formatted reports from your most recent test run:

# Print summary to terminal maeris report tests # Export as HTML (visual dashboard) maeris report tests --format html --output test-results.html # Export as JSON (for CI/CD integration) maeris report tests --format json --output test-results.json # Export as CSV (for spreadsheet tracking) maeris report tests --format csv --output test-results.csv # Filter by folder maeris report tests --folder Authentication --format html

The HTML report includes:

Pass/fail summary with trend chart over last 10 runs
Per-test duration and result breakdown
Failure details with screenshot at point of failure
Step-by-step execution timeline for each test
Auto-fix history showing which selectors were repaired

Coverage Reports

Generate a unified coverage report combining UI and API coverage in a single document:

maeris report coverage maeris report coverage --format html --output coverage-report.html

Security Reports

Generate a security findings report from your most recent security scan:

maeris report security maeris report security --format html --output security-report.html maeris report security --format csv --output findings.csv maeris report security --min-severity high

The check_api_coverage MCP Tool

When working through your AI editor, the check_api_coverage MCP tool compares your codebase's API surface (discovered via static scan) against the flows and assertions you have defined in Maeris. It returns a gap analysis you can act on immediately:

Example prompt to Claude Code

"Check my API coverage and tell me which endpoints are missing tests" — Claude Code calls check_api_coverage and presents the gap analysis with recommendations for which endpoints to add assertions to first.

The tool returns:

Total endpoints discovered vs total with assertions
Coverage percentage by collection and sub-collection
List of uncovered endpoints sorted by usage frequency
Suggested assertion types for each uncovered endpoint based on its method and URL pattern

Scheduling Reports in CI/CD

To generate reports automatically in a CI/CD pipeline, add the relevant commands to your pipeline script:

# In your GitHub Actions or CI script:
maeris test run --regression
maeris report tests --format json --output results.json
maeris coverage api --format json --output api-coverage.json

# Optionally push results to portal for team visibility
maeris push tests
maeris scan push

Tip: Use the JSON report format in CI/CD so downstream tools (Slack notifications, dashboards, issue trackers) can parse results programmatically. HTML reports are best for human review and sharing with stakeholders.

Next Steps

For a complete reference of all available MCP tools, see the Available MCP Tools Overview.