Where does a run actually write its files? I cannot find the report

Asked 19 Nov 202016,210 views3 answers

44votes

First real run finished and the console printed the totals, but I have no idea where anything landed. I was expecting a reports/ folder next to features/.

bash

sdods run -p demo-shop -e staging -l ui -b chromium -t @smoke

There is a .sdods directory in the workspace root. I do not want to poke around in it blind — what is in a run directory, and which file am I supposed to open?

reporting cli

asked by Hsu Wei-lin15,230 · 19 Nov 2020

3 answers

58votes✓
Accepted answer
Everything a run produces goes under .sdods/runs/<runId>/. The run id is a UUID v7, so the directories sort by time on their own.
text
```
.sdods/runs/<runId>/
  run.json                     manifest: project, env, tags, browsers, git, command
  summary.json                 totals and status
  messages.ndjson              cucumber messages, the canonical ingest format
  playwright-report/           the HTML report
  dashboard/                   index.html + metrics.json
  demo-shop/<fingerprint>/r0/  one directory per scenario attempt
```
You do not have to find it by hand:
bash
```
sdods report --last --open
```
That prints the totals and the report paths, then opens the HTML report and the dashboard. The dashboard is the one to send round: it is self-contained and survives being mailed.
sdods run --artifacts-dir <dir> writes the tree somewhere else. If you do that, set SDODS_ARTIFACTS_DIR too, because report only learns the new root from the environment variable.
View results has the full layout.
answered by Reeta Nandalmaintainer41,280 · 19 Nov 2020
11votes
And when you want it in a script rather than on a terminal, sdods report --last --json gives you { runId, dir, manifest, summary, reports } as one object. Much better than parsing the table.
answered by Marijn Kuiper18,840 · 20 Nov 2020
6votes
The bit that took me a while to appreciate: the <fingerprint> directory under the project slug is stable across runs and across browsers. So the same scenario in run A and run B is the same path, and diffing two runs by eye actually works.
r0 is the first attempt, r1 the first retry, and so on. Inside each you get meta.json, scenario-start.png, scenario-end.png, failure.png when it failed, the numbered before/after step images, and api/ for API steps.
answered by Dinuka Perera412 · 4 Dec 2020

Have the same question?

Ask it with the command you ran and the output you got, and it will be answered here.

Ask a question

Where does a run actually write its files? I cannot find the report

3 answers

Related