Export

Three reports export as PDF, JSON, and JUnit XML:

PDF is for people who don't have the app: a test manager, a customer, an auditor. JSON is for your own toolchain: a dashboard, a quality gate, or a test management system. JUnit XML is for the test report view of your CI system, such as Jenkins or GitLab.

Export a report

1. Open the execution report or the summary report on the Runs page.
2. Click Export. Above an execution report, it sits in the header row with the test's name, which stays visible while the report scrolls.
3. Pick Export as PDF, Export as JSON, or Export as JUnit XML.
4. Pick the folder and the file name in the save dialog.

The save dialog opens in the project's reports/ folder. The first export creates that folder. You can pick any other location.

For an execution report, you can also right-click the test and pick Export as PDF, Export as JSON, or Export as JUnit XML. The entries appear once the test's report is written. The Management Report has its own steps: Create a report.

If the export fails, AskUI Desktop shows the error and writes no file. A half-written file never replaces an existing one.

Every PDF has the AskUI design. Statuses appear as labelled markers, for example PASSED.

• Execution report and run summary: no cover and no end page. The PDF opens with a dark header band: the AskUI logo, Execution report or Run summary, the test or plan name, and the facts (status, duration, cost, run, device, model).
• Management Report: a dark cover page, numbered sections, and a dark end page: What the report shows.

Every page except a cover and an end page has a running header (the AskUI mark, the project and the kind of document) and a footer (Generated with AskUI Desktop with the date and time, and Page n / m).

The first PDF export

AskUI Desktop prints PDFs with a Chromium browser. If it is missing, the first PDF export downloads it once, about 170 MB. This export takes longer. The download and its cache are the same as for runs on a web browser profile, so a machine that already ran a web test downloads nothing.

The JSON documents

Every JSON document starts with two fields:

• schemaVersion: the version of the document's layout, currently 1. A new version means a field changed meaning or was removed.
• kind: execution-report, run-summary, or management-report.

Read kind first, then the fields of that kind. Times are ISO 8601 with a time zone offset. A value that is unknown is null.

The run

The execution report and the run summary both carry a run object:

Counts

The run summary and the Management Report count results in a counts object: counts in the run summary and in each test and run entry of the Management Report, and totals at the top of the Management Report. Every counts object has the same fields:

{ "passed": 11, "failed": 1, "broken": 0, "warnings": 2, "notCounted": 3,
  "executed": 12, "passRate": 92, "allGreen": false }

Execution report

{
  "schemaVersion": 1,
  "kind": "execution-report",
  "run": { "folder": "2026-10-05_09-00-00", "device": "Staging browser", "...": "..." },
  "test": "login_test",
  "file": "/projects/shop/tests/login_test.md",
  "status": "FAILED",
  "reason": "Expected the dashboard, saw an error banner.",
  "startedAt": "2026-10-05T09:00:00+00:00",
  "endedAt": "2026-10-05T09:01:12+00:00",
  "markdown": "# Test Case Report: login_test\n...",
  "writer": {
    "state": "ready",
    "writtenAt": "2026-10-05T09:01:40+00:00",
    "model": "claude-sonnet-5",
    "inputTokens": 21500,
    "outputTokens": 1180,
    "cacheReadTokens": 0,
    "cacheWriteTokens": 0,
    "cost": 0.0822,
    "error": null
  },
  "cost": { "execution": 0.3315, "report": 0.0822, "total": 0.4137 }
}

Run summary

Management Report

The same runs and the same choices give the same Management Report JSON, byte for byte. It has no timestamp of its own and no text from a model.

JUnit XML

The root of every JUnit XML file is <testsuites>. Inside it:

In an execution report, each screenshot is one line of this form, after the Markdown:

[[ATTACHMENT|<absolute path>]]

Jenkins, with the JUnit Attachments plugin, and GitLab read these lines and show the screenshots next to the test.

The statuses map to JUnit like this:

Each <testcase> has the test file as its classname. Each <testsuite> carries the plan, the device, the model, and the app version as properties.

AskUI Desktop writes these files and does not read them back. To keep a report inside the app, keep the run folders.