-
Notifications
You must be signed in to change notification settings - Fork 40
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
Output during tests execution #45
Comments
OndraM
added a commit
to OndraM/steward
that referenced
this issue
Jan 29, 2016
OndraM
added a commit
to OndraM/steward
that referenced
this issue
Jan 29, 2016
OndraM
added a commit
to OndraM/steward
that referenced
this issue
Jan 29, 2016
OndraM
added a commit
to OndraM/steward
that referenced
this issue
Feb 12, 2016
…readability (part of lmc-eu#45)
OndraM
added a commit
to OndraM/steward
that referenced
this issue
Feb 12, 2016
OndraM
added a commit
to OndraM/steward
that referenced
this issue
Feb 12, 2016
OndraM
added a commit
to OndraM/steward
that referenced
this issue
Feb 13, 2016
OndraM
added a commit
to OndraM/steward
that referenced
this issue
Feb 13, 2016
OndraM
added a commit
to OndraM/steward
that referenced
this issue
Feb 13, 2016
…readability (part of lmc-eu#45)
OndraM
added a commit
to OndraM/steward
that referenced
this issue
Feb 13, 2016
OndraM
added a commit
to OndraM/steward
that referenced
this issue
Feb 13, 2016
#46 is now merged, will be released in 1.3.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently output of all tests is printed in the console output right after each test is finished. This makes the output a bit messy and is not always necessary. We should use output levels (default, verbose, very verbose, debug) to make the output more helpful in different situations.
Output levels distribution
Standard level
Use-case: I just want to run everything and I care only about test results count, not about the cause of errors etc.
Verbose level (
-v
)Use-case: I want to run tests locally and see some basic startup/status/progress information during the run. If some test fails, I want to know which one. (But don't care about exact error message.).
Very verbose level (
-vv
)Use-case: I want to run tests locally and see detailed startup/status/progress information during the run. If something happens during the run, I want to know where and what exactly.
Debug level (
-vvv
)Use-case: I am debugging some tests and want all available information, see what starts and when; OR the tests are run on CI server (and the output is stored for possible later investigation)
Uncategorized messages
Messages from the PHPUnit process
Any thoughts, ideas, comments?
The text was updated successfully, but these errors were encountered: