Test colors and no-colors outputs
Open
tests
- Dominant language
- Python
- Stars
- 140
- Forks
- 45
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/1202)
In GitLab by [[Gitlab user @traveltissues]](https://gitlab.com/traveltissues) on Nov 12, 2019, 10:50
https://gitlab.com/BuildStream/buildstream/merge_requests/1704#note_243326092
Add a test checking that `--no-colors` is being respected (guard against regression on #1200)
Contributor guide
Research direction
Start by locating the CLI test coverage for `--no-colors` and compare it with the color-enabled output; use the regression described in #1200 and the linked merge-request discussion as context. Done means tests cover both colored and no-color output and fail if `--no-colors` is ignored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100