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.
Our QA lead wants Allure because that is what the other teams publish. I am happy to produce it, but the last time I touched a reporter list in another tool I lost everything else that was in it, and our ingest depends on the ndjson.
Does --allure replace the default reporters or add to them? And can I turn it on for the project instead of remembering a flag?
Adds. The defaults — console, HTML report, cucumber messages NDJSON and the SDODS dashboard — are always emitted. --allure appends allure-playwright writing into <runDir>/allure-results, and --reporter <name[=outputFile]> appends whatever else you name. A reporter already in the default list is skipped rather than added twice, which is why --reporter junit in CI does not leave you with two JUnit files fighting over one path.
For the project, put it in the yaml and drop the flag:
reports:
allure: true
junit: true
cucumberHtml: falseOne thing that gets confused with this: --reporter-mode is unrelated. It only swaps the console reporter between list, line and dot and never touches the file reporters.
Worth knowing where path-less reporters land, because it is the run directory and not your working directory:
--reporter junit writes <runDir>/junit.xml--reporter blob writes <runDir>/shard-reports/--reporter json writes <runDir>/runner-results.extra.jsonname=outputFile overrides that when your publisher insists on a fixed path. The blob one is the one that matters for sharding — those directories are what you download and feed to sdods report merge.
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.