I am fixing one scenario in a feature that has eleven of them. Running the feature each time costs me two minutes per attempt, most of which is scenarios I am not touching.
What is the narrowest thing I can run?
asked by Nikhil Sane
Running one scenario without waiting for the whole feature file
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.
1 answer
Accepted answer
Three levels of narrowing, from coarse to fine:
bashsdods run -p demo-shop -e staging --feature cart/cart.feature sdods run -p demo-shop -e staging --scenario "Removing the last item" sdods run -p demo-shop -e staging --grep "last item|empty cart"--featureis a path relative tofeatures/.--scenariomatches scenarios whose title contains that text, which is the one you want here.--grepis a regular expression against the test title if the substring is not selective enough.While you are iterating, add
--headed --debugand watch it fail at the step. Do not leave either in anything committed — they need a display and a person.answered by Rafa Garrido
Know the answer?
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.
Related
- Linting only the staged feature files in a pre-commit hook — is --json stable enough?0 answers
- har record printed no scrub line and the Cookie header is still sitting in the file0 answers
- Can --explain show the values a layer lost with, not just the winner?0 answers
- Six locales times dark and light means twelve env files — is there a per-scenario way?0 answers
- Does --repeat-each 5 with --shard 1/4 repeat inside the shard or across shards?0 answers