Skip to content
Marriska Docs

How to share a test run report

When a run finishes (or fails), you usually want someone else to look at it. This guide covers the four ways Marriska lets you do that.

Section titled “1. Send the in-app link”

  1. Open the report

    From Reports in the top nav, click the row for the run you want to share.

  2. Copy the URL from your address bar

    Reports have stable, deep-linked URLs (e.g. /reports/abc-123 for a single test, /reports/set/xyz-456 for a test set run).

  3. Send it

    Anyone in your org with the role to view reports will land on the same view you’re seeing — full step list, screenshots, timings.

2. Auto-notify on schedule runs

Section titled “2. Auto-notify on schedule runs”

When you create a schedule, you can list email addresses to notify when the run completes. Notification emails include a direct link to the report. See Scheduling tests for the setup.

Toggle Notify on failures only if you want quiet runs to stay quiet — good for catching regressions without drowning the channel in green-status emails.

The same recipients have to be members of the org to actually open the report from the email link.

3. Export the test as code

Section titled “3. Export the test as code”

The report detail page exposes per-execution exports for downstream tools. They’re useful for:

  • Embedding in a code-review or PR comment as proof of behavior
  • Handing the test to an engineer who’d rather work with raw Playwright
  • Archiving offline
FormatWhat it containsEndpoint
YAMLThe compiled step list the executor ranGET /api/v1/tests/{execution_id}/yaml
JSONStructured execution metadataGET /api/v1/tests/{execution_id}/json
.marriskaSelf-contained bundle (steps, original text, language, platform) — re-importableGET /api/v1/tests/{execution_id}/export/marriska
PythonRunnable Playwright Python scriptGET /api/v1/tests/{execution_id}/export/python

These return file downloads with the appropriate Content-Disposition headers. Hit them directly with a session-authenticated browser, or from CI with an API key.

4. Forward a screenshot

Section titled “4. Forward a screenshot”

Every step screenshot has its own URL (/api/v1/tests/{execution_id}/screenshots/{browser}/{step_number}) and is fetched directly from the API. The lightbox in the report view opens the screenshot full-size — right-click → Save image to attach it to a Slack message or ticket.

For visual-regression failures, the report shows the captured screenshot side-by-side with the baseline; both are downloadable the same way.

What’s not yet supported

Section titled “What’s not yet supported”
  • Public share links / view-without-account. No share-token endpoint exists today. Anyone you send a report URL to must sign in to your org first.
  • PDF export. The HTML view is the only render — there’s no one-click PDF.
  • Slack-direct sharing. The notification path is email-only for now.
Section titled “Related”