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.
I pointed the CLI at staging and asked for the API layer only:
sdods run -p demo-shop -e staging -l apiIt printed nine passing scenarios and was finished before I had read the command back. No browser window, no window flashing past, nothing. Coming off a Selenium suite where nine tests is a coffee break I do not believe it.
Is -l api some kind of dry run, or did it really talk to the environment?
Accepted answer
It really ran. -l api selects the API layer, which drives HTTP requests directly and never starts a browser — that is the whole point of the layer, and it is why the same nine scenarios take two seconds instead of two minutes.
If you want proof rather than a feeling, the run leaves it on disk:
cat .sdods/runs/<runId>/summary.jsontotals there is the same count the terminal printed, and run.json records the command, the env and the exit code. The dry run you are thinking of is --list, which prints the run targets and the tests that would run and then stops.
The speed is the feature. An API-layer run is cheap enough to put in a pre-commit hook, which is not true of anything that opens a browser.
If you still distrust it, break it on purpose: stop the application and run the same command. Every scenario fails with a connection error instead of an assertion failure, which tells you the suite was genuinely reaching the environment before.
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.