User Guide

Navigation

The sidebar is organized into clear sections:

Dashboard

The dashboard shows aggregate metrics across all stored reports:

• Total runs — ingested TestRunReport documents
• Suites executed — sum of suite counts across runs
• Passed / failed — suite-level outcomes
• Pass rate — percentage of suites that passed

The Projects & tags section lists groupings from pushed metadata. Click any chip to open the test runs page with that filter applied.

Recent runs shows the latest reports with project, tags, framework, and result badges. Use View all for the full filterable list.

Test runs — search and filters

The test runs page is designed for finding specific reports quickly without bias toward any single filter.

Search bar

Search across label, project, framework, and tags. Input is debounced (300ms) so typing does not trigger excessive API calls.

Quick filters

One-click presets at the top:

Active filter chips

When filters are applied, chips appear below the search bar showing exactly what is active. Click a chip to remove that filter, or use Clear all.

Advanced filters

Expand Advanced filters for project, framework, status, date range, and tag selection. When multiple tags are selected, choose:

• Match any — runs with at least one selected tag (OR)
• Match all — runs that have every selected tag (AND)

Columns

Import report

Upload a TestRunReport JSON file when you are not pushing programmatically. Optionally set project and tags before upload — they are stored as searchable metadata.

Accepted format

The file must be a valid TestRunReport JSON object. Minimum required fields:

{
  "generatedAt": "2026-07-07T10:00:00.000Z",
  "framework": "@vaagatech/snapline-engine",
  "summary": { "total": 1, "passed": 1, "failed": 0 },
  "suites": [
    {
      "name": "My suite",
      "passed": true,
      "results": [{ "step": "api", "passed": true }]
    }
  ]
}

How to upload

1. Drag a .json file onto the drop zone, or click to open a file picker
2. Hub parses and validates the JSON
3. On success, the label defaults to the filename (without .json)
4. You are redirected to the run detail page

Common upload errors

Run Detail

Each stored report has a unique UUID. The detail page shows:

Header

• Run label and framework name
• Generation timestamp
• Delete button — permanently removes the report from SQLite

Summary cards

Total suites, passed count, failed count, and duration (summary.durationMs).

Environment

If the report includes an environment object (set via buildReport meta), each key-value pair is displayed — e.g. baseUrl, reportFormat, suiteName, CI build IDs you add yourself.

Failures section

When any step failed, a highlighted Failures section appears at the top listing every failed step across all suites, with full diff blocks. This lets you diagnose issues without expanding each suite manually.

Suites

Each suite is a collapsible card:

• Suite name — from TestSuiteResult.name
• Step counts — total, passed, failed
• PASSED / FAILED badge

Failed suites are expanded by default. Passed suites are collapsed. Click the header to toggle.

Understanding step results

Each step in a suite maps to a TestStepResult:

Fixture case semantics

For runApiFixtureCases / run_snapline_fixture_cases:

• step is the case directory name (e.g. 04-fail-segment-mapping), not the human-readable name from case.json
• Cases with expectMatch: false pass when Snapline finds a mismatch — Hub shows them as passed steps
• Auth failure cases (expectStatus: 401) pass when HTTP 401 is returned

Diff viewer

When a step fails, Hub renders the Snapline DiffResult:

{
  "path": "segment",
  "actual": "premium",
  "expected": "standard",
  "message": "Value mismatch"
}

• path — dot-path to the first mismatch (depth-first). Nested fields use dots; array indices use brackets: orders[0].status
• actual — value from the live/processed side after transforms
• expected — value from the expected fixture after ignoreFields
• message — mismatch category: Value mismatch, Type mismatch, Missing key, etc.

Labels

Labels help identify runs in the UI. Set them when pushing:

// Node.js
await pushTestReportToHub(report, { hubUrl: '...', label: 'CI build #4821' });

// Python
push_test_report_to_hub(report, hub_url='...', label='CI build #4821')

// Env
SNAPLINE_HUB_LABEL="nightly-$(date +%Y%m%d)" SNAPLINE_HUB_URL=... npm run demo

When uploading, the filename (without extension) becomes the label.

Deleting reports

On the run detail page, click Delete and confirm. This removes the report from SQLite permanently. There is no undo.

API equivalent: DELETE /api/reports/:id — see API Reference.