rtfeldman / rtfeldman/node-test-runner
Feature request: allow multiple `--report` flags
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 83
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 5
Description
I'd love to be able to run elm-test --report junit.xml --report console. This would allow me to program a single command that runs both in CI and on developmen.
Benefits of doing this over having separate commands for CI and local development:
- Less complexity (branching) in my test harness code. For example, the example command above could be copied as is into a
package.jsontesthook and makenpm testdo something useful in CI and on development. - Fewer differences between how tests run on CI and locally means there's a smaller chance that problems on CI proof difficult to reproduce locally.
It would mean that elm-test would need to be able to run XML output directly to a file, to avoid printing human-readable and XML output both to stdout.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the elm-test CLI handling for --report and trace how report destinations are selected. Verify the behavior for repeated flags such as --report junit.xml --report console, including writing XML to the requested file while retaining console output; done means both reports are produced from one command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100