acceptance tests: add flags to control output
Open
Nobody has claimed this yet.
testing
- Dominant language
- Jupyter Notebook
- Stars
- 5
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 17
Description
Add flags to acceptance test output for:
- Including generated code
- Showing full output for all tests (not just fails)
- Terse output (pass / fail only? Include fail reason?)
Flags passed to the command line
Contributor guide
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 acceptance test command-line entry point and inspect how test output is currently generated. Define flags for including generated code, showing full output for every test, and using terse pass/fail output, including the expected failure detail behavior. Done means each flag changes the command output as specified and the acceptance tests cover the modes.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100