-
Notifications
You must be signed in to change notification settings - Fork 8
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
Use less verbose test output formatter #1333
Conversation
55c4af8
to
b1a2b1a
Compare
b1a2b1a
to
f4e9950
Compare
Mhm, per default i would only activate the middleground for rspec (where it is really necessary). For cucumber i think that the verbose output is actually necessary/extremely useful. |
I think verbose output in cucumber is only useful when something fails. Otherwise it's just some green text that you don't read anyway. At least I don't. In my opinion it clutters the console. We don't have that many cucumber features at this point, but when it gets more, I think we really want to shorten the output. |
Yeah, but you do not get the full output for a failing test, and i think for cucumber (with their step-system) it is important to see them all. |
@ebolloff want to be the tie-breaker? |
Yes, then I think I should change the formatter to print the full output of a failing test. |
If that would be possible, it would probably be the optimal case. |
f4e9950
to
3b52fdd
Compare
3b52fdd
to
6be3cde
Compare
How about now? a44c794 "Print failure details after the features." should add the details. |
👍 |
…rmatter Use less verbose test output formatter
The quite verbose formatter annoyed me a little because it printed way more information than we needed. This pull request adds formatters that combine the strengths of the very verbose formatters
documentation
(for rspec) andpretty
(for cucumber) and of the too little printing formatterprogress
.Those are only active by default on development machines. I made sure that the verbose formatters are used on travis and jenkins.
rspec
cucumber