Inherited a project with about ninety scenarios and no tags at all. Ran:
sdods lint -p shop --fix-tagsIt rewrote the files and the layer errors are gone, which is great. But every tags/suite error is still there, and it also did not touch some of the layer ones. Is this a bug, or is it refusing on purpose?
Accepted answer
On purpose, and the rule is that it only writes a tag it can derive from something you already told it.
It fixes two things:
features/ui/, features/api/ or features/hybrid/ segment, or when the owning module declares layers. Note "missing" — if the scenario already has two layer tags it will not pick one to delete.It never guesses a suite tag, because nothing in your project says whether a given scenario is smoke, regression or sanity. That is a judgement about what the scenario is for, and a tool that guessed it would fill your smoke suite with ninety scenarios and be wrong about most of them.
The layer ones it skipped are the ones where neither signal was available — a file under a module with no layers and no layer segment in the path. Declare layers on those modules and run it again.
Two practical notes since it edits your working tree in place.
It appends to an existing tag line when there is one directly above the scenario, and inserts a new line at the scenario's indentation when there is not. That is fine but it is a real edit — commit or stash before running it so the diff is reviewable.
For the suite backlog, do it per module rather than per file. Decide "everything in features/checkout/ is regression except these three", add the tag, re-lint. Ninety scenarios is two afternoons, and the alternative is a suite nobody trusts.
Have a different question? Ask it.