Upload Reports

After a run, the configured outputDir contains run_<runId>.json, its HTML report, and any screenshots under screenshots/run_<runId>/.

Upload:

testronaut login
testronaut upload
testronaut upload run_1788745106444
testronaut upload missions/mission_reports/run_1788745106444.json

The command selects the newest report from outputDir. It uploads only screenshots referenced by that report, so screenshots from older or concurrent runs are not sent. Older reports that reference the legacy shared screenshots/ directory remain supported.

Uploaded reports include the CLI version and retain both the human-readable mission name and source mission filename.

After upload, use the Mission Control dashboard to search by any of those identifiers, filter by status or tags, sort runs, and inspect screenshots and turn details.

Upload only report JSON when screenshots are not needed:

testronaut upload run_1788745106444 --no-upload-screenshots

Under the hood

Auth via API key.

The server derives the user from the session token and stores the report metadata and JSON.

testronaut serve and Mission Control are separate views: serve reads local files, while Mission Control shows uploaded reports.

Under the hood​

Under the hood