Plan Run Report

A Test Plan report shows the outcome of a run and its individual steps. Use it to investigate a failed step, share results with a teammate, or publish a CI result. You can open the run in Mockarty or download one of six formats.

About URLs in examples: replace localhost:5770 with your Mockarty address if the server runs elsewhere.

Related pages: Run View · Override Surfaces · Test Plans · Test Plans in CI/CD

What the report contains

The report identifies the plan and run, shows their timing and result counts, and lists the result of each item. Depending on the item, details may include test steps, measurements, findings, or attachments. A nested Test Plan appears under its parent item; when its run reference is available, the child plan name links to that run. Skipped items include a reason when one is available.

Check the overall run status alongside the counters. A run with skipped or unknown items is not described as fully passed, even when no individual failure appears in the report tree.

Open a run from Test Plans → Runs to inspect its items before exporting. The exact detail shown depends on the test engine and on the data available for that run.

Per-format use cases

The six downloads for a Test Plan run are:

Each suffix follows this URL:

/api/v1/namespaces/:namespace/test-plans/:idOrNumericID/runs/:runID

For example, to save JUnit XML for a run:

mockarty-cli testplan report <runID> --plan <planID> --format junit -o report.junit.xml

The HTML report includes its styles and can be saved as a PDF through your browser’s print dialog. report.html?standalone=true requests the attachment-inlining variant for offline sharing; this can make the file larger. Check the downloaded file before sharing it if it contains test data or attachments.

Reports of other engines

Mockarty also has a unified run view at /ui/runs/<kind>/<id>/report for supported run kinds. Its API is /api/v1/runs/<kind>/<id>/report. Use Test Runs for that view and its CLI command; the six URLs above apply specifically to Test Plan runs.

For that unified API, ?format=allure_zip and ?format=allure_dir include the report’s referenced attachments. If an attachment cannot be read, the download fails instead of returning an archive missing that file. Check the attachment storage and retry the export.

Large-run streaming

When a stored Allure or HTML artifact is available, Mockarty serves it from artifact storage. If it is missing, Mockarty generates the report from the run. Large reports and attachments can take longer to download, so keep the browser open until the file is complete.

Security: redaction guarantees

Mockarty masks recognised secret fields in saved plan context and report parameters. Before sending any downloaded report outside your team, review its contents: test requests, responses, and attachments can contain data from the system under test. Restrict access to the report as you would restrict access to the test run.

Common pitfalls

• No report yet: check that the run has finished and that you selected the correct plan and run IDs.
• CI does not display the result: download JUnit XML and confirm that your CI job publishes that file as a test report.
• HTML is too large to share: use the ordinary HTML download or a concise Markdown summary instead of the attachment-inlining variant.

Permissions

Report downloads follow the plan’s namespace access rules. If a URL works for a teammate but returns an access error for you, ask an administrator to check your access to that namespace and plan.

Next: Override Surfaces explains how to change plan inputs; Run View explains the live run screen.