-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Added console-lines
output mode which prints each test on a separate line
#443
Conversation
console-lines
mode which prints each test on a separate lineconsole-lines
output mode which prints each test on a separate line
I like that! I'd probably just use a slightly different name, like |
I'd think So if you'd prefer |
21d770f
to
415bb2b
Compare
console-lines
output mode which prints each test on a separate lineverbose
output mode which prints each test on a separate line
Updated: Renamed to |
I was just throwing that out there, I'm sure someone can think of something better. |
Imho 'console-lines' was better. Or just 'lines'? |
I think the word So for now I changed it back to |
…ine. This is handy for environments with non-standard (buffered) handling of standard output, for example Github Actions (where a progress of tests cannot be seen until until end-of-line appears, which in standard `console` mode happens only when all tests finish) or Docker Compose logging output, where in standard `console` mode each finished test's dot is printed alone on separate line. Or the console-lines mode can be handy just to see a more detailed progress of tests in all environments, because it outputs something like this: ``` · 1/85 Framework/Assert.contains.phpt OK in 0.14 s · 2/85 CodeCoverage/PhpParser.parse.edge.phpt OK in 0.17 s · 3/85 CodeCoverage/PhpParser.parse.lines-of-code.phpt SKIPPED in 0.18 s · 4/85 CodeCoverage/PhpParser.parse.lines.phpt FAILED in 0.19 s ... ``` Also, "cider mode" now shows a lemon emoji for skipped tests.
415bb2b
to
b6b18a3
Compare
verbose
output mode which prints each test on a separate lineconsole-lines
output mode which prints each test on a separate line
What do you mean, @milo? |
95674fc
to
c5eff68
Compare
…ine. (#443) This is handy for environments with non-standard (buffered) handling of standard output, for example Github Actions (where a progress of tests cannot be seen until until end-of-line appears, which in standard `console` mode happens only when all tests finish) or Docker Compose logging output, where in standard `console` mode each finished test's dot is printed alone on separate line. Or the console-lines mode can be handy just to see a more detailed progress of tests in all environments, because it outputs something like this: ``` · 1/85 Framework/Assert.contains.phpt OK in 0.14 s · 2/85 CodeCoverage/PhpParser.parse.edge.phpt OK in 0.17 s · 3/85 CodeCoverage/PhpParser.parse.lines-of-code.phpt SKIPPED in 0.18 s · 4/85 CodeCoverage/PhpParser.parse.lines.phpt FAILED in 0.19 s ... ``` Also, "cider mode" now shows a lemon emoji for skipped tests. Co-authored-by: David Grudl <[email protected]>
Usage example:
This is handy for environments with "non-standard" (buffered, I guess?) handling of standard output, for example
Github Actions
(where a progress of tests cannot be seen until until end-of-line appears, which in standardconsole
mode happens only when all tests finish) orDocker Compose
logging output (where in standardconsole
mode each finished test's dot is printed alone on separate line).Or the
console-lines
mode can be handy just to see a more detailed progress of tests in all environments, because it outputs something like this:Also, "cider mode" now shows a lemon emoji for skipped tests.