Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Tagged a scenario @data:orders on the assumption that it would put the columns in scope the way @user:standard puts an account in scope. The scenario runs, lint is clean, and the assertion fails with the placeholder still in it:
Expected to see the text "{{orderId}}"So it clearly did not load. Is the tag broken, is it doing something else, or did I invent the behaviour?
Accepted answer
You invented the behaviour, but it was a reasonable guess because the two tags look symmetrical and are not.
@user:<role> has a run-time effect: it leases an account before the browser context is created so the scenario starts logged in. @data:<dataset> is a fact about the scenario, not an instruction — lint validates that the dataset exists in data.sources, and that is the whole of it. Nothing is loaded.
Load rows explicitly:
Given I load dataset "orders" row 0The literal {{orderId}} in your failure is the general tell, by the way. An unresolved placeholder renders as itself rather than as an empty string, precisely so this shows up in the assertion instead of quietly comparing against nothing.
The tag still earns its keep: when the dataset changes, it is how you find everything that depends on it.
sdods run -p shop -e staging -t "@data:orders"Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.