New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suppress console coverage report with `--quiet` #2370

Merged
merged 1 commit into from May 30, 2016

Conversation

Projects
None yet
3 participants
@EspadaV8
Contributor

EspadaV8 commented Sep 15, 2015

PR for #1592

This should work as-is, although I'm not sure it's the 'right' way of doing it. When --quiet is used it also suppresses the progress of the tests, which isn't really what I would find useful, ideally I'd like to see the test progress but just hide the report. That would require a new option (something like --no-coverage-console or --coverage-quiet) and I wasn't sure if that would be okay so I thought I'd check first.

@DavertMik DavertMik added the Discuss label Sep 15, 2015

@Naktibalda

This comment has been minimized.

Show comment
Hide comment
@Naktibalda

Naktibalda May 24, 2016

Member

@DavertMik No comments in 8 months, can I remove RFC label and merge it?

Member

Naktibalda commented May 24, 2016

@DavertMik No comments in 8 months, can I remove RFC label and merge it?

@DavertMik

This comment has been minimized.

Show comment
Hide comment
@DavertMik

DavertMik May 30, 2016

Member

Oh, absolutely forgot about it. Sorry. Probably I thought this was something different than that... Anyway, seems reasonable

Member

DavertMik commented May 30, 2016

Oh, absolutely forgot about it. Sorry. Probably I thought this was something different than that... Anyway, seems reasonable

@DavertMik DavertMik merged commit 1cdae11 into Codeception:2.1 May 30, 2016

2 checks passed

continuous-integration/appveyor AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@DavertMik DavertMik removed the Discuss label May 30, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment