Reporting

Every BrowseGenius run produces an evidence bundle that teams can archive, share, or attach to defect reports. This page explains what gets recorded and how to customise the output.

Artifact types

Artifacts are appended to the active report as the suite executes:

Type	Description
log	Human-readable messages (actions, parser notes, failure reasons).
dom	Sanitised DOM snippets or fragments captured during validations.
screenshot	Base64 PNGs captured on demand (future roadmap: automatic per-step snaps).
video	Placeholder slot for tab-capture recordings (planned enhancement).

Each artifact includes a timestamp and the originating test case ID so you can correlate events during analysis.

Summary fields

The final report contains:

• Suite status (complete, error, or running while in progress).
• Case list with final status, failure reason (if any), and duration in milliseconds.
• Aggregated counts (total, passed, failed, blocked, skipped).
• Start and completion timestamps.

Downloading bundles

• Use the Download report button in the popup footer.
• The extension saves:
  • browsegenius-report-<timestamp>.json
  • browsegenius-report-<timestamp>.html
• Files are generated via chrome.downloads.download, so you may be prompted for permission the first time.

HTML report layout

The VitePress docs include a sample template. Key sections:

1. Summary card — high-level metrics and timing.
2. Cases table — per-case status, duration, and failure explanations.
3. Artifacts list — chronological entries including embedded screenshots.

You can customise the layout by editing src/services/reportBuilder.ts. Suggestions:

• Filter artifacts (e.g., only include failed-case entries).
• Embed GIF/video timelines when tab capture is added.
• Add markdown-to-HTML rendering for richer notes.

Integrating with QA tooling

• Upload JSON into your defect management system to retain structured data.
• Convert JSON to JUnit/Allure for CI dashboards (planned example scripts).
• Store HTML in SharePoint/Confluence for audit trails.

The JSON schema is stable and lives in SuiteReport within src/state/testPlanner.ts.