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.
Wanted local runs on chromium only while staging keeps all three, so I put this in envs/local.yaml:
browsers: [chromium]No error. sdods run -p demo-shop -e local -l ui --list still lists chromium, firefox and webkit targets. If the key is wrong I would rather be told.
Accepted answer
There is no browsers key in the environment schema, and unknown keys are dropped rather than rejected — so your line is parsed, discarded, and never reaches anything.
Browsers are a project-level decision. An environment describes where the app is, not how you drive it, and the only project sections an environment file may patch are screenshots, heal, timeouts and perf.
Three ways to get what you want:
sdods run -p demo-shop -e local -l ui -b chromiuma process with browsers: [chromium] for the recipe you repeat, or SDODS_* in a shell profile if it is really per-machine. The flag is layer 6 and wins over everything.
You can prove it in one command rather than by running a suite:
sdods config show -p demo-shop -e local --explainproject.browsers will say project. If the env file had contributed anything the layer would read envYaml.
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.