Screenshots and visual testing says:
Baselines live under projects/<slug>/features/__screenshots__/<browser>/What is actually on disk after a run:
projects/demo-shop/features/__screenshots__/demo-shop--ui--chromium/darwin/inventory.pngTwo extra segments and neither of them is just the browser. I want to write a cleanup script that prunes baselines for browsers we dropped, so I would rather know the real rule than pattern-match on what I can see today.
Accepted answer
The two segments are the run target and the platform.
demo-shop--ui--chromium is the run target name: project slug, layer, browser, joined with a double dash. The API layer has no browser so its targets are two segments, but the API layer never takes a screenshot.darwin is the platform the baseline was recorded on.So the real rule is __screenshots__/<project>--<layer>--<browser>/<platform>/<name>.png. Dropping a browser means deleting one directory per platform, not one directory.
To be exact about where it comes from: the runner config sets the snapshot path template to {projectName}/{platform}/{arg}{ext} under <project root>/features/__screenshots__, and {projectName} is the run target, not the SDODS project.
The guide's shorthand predates the layer being part of that name and is wrong. Known limitations is closer — it has the platform — but writes <project> where it means the run target. Both want a fix; thank you for reading them side by side.
Practical consequence nobody mentions until it bites: adding a browser to browsers: in the project yaml creates a whole new baseline tree, empty, for every platform you run on.
browsers: [chromium, firefox, webkit]That is one line in review and six directories of missing baselines in the nightly. Add browsers to @visual deliberately, not as a side effect of widening the matrix.
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