-
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
Command line option to disable printing World
when there are failed tests or panics
#192
Comments
cc @ilslv |
@ilslv also, I think it's worth to bind it to the exisiting |
@tyranron I would split them, because I think that default behaviour should be "print failed world, but not the docstring". One reason for that is I saw some of users of this crate using docstrings as some kind of spec, including graphql query there for example |
@ilslv what about verbosity levels? |
@tyranron good idea 👍. I don't think there will be a case when someone wants to print docstrings, but not the world. |
@ilslv so, let's do it this way. |
If there is no verbosity option passed, nothing will be printed? Or will you add a default option? |
I believe that by default we should print |
@ilslv why not just |
@yds12 @theredfish what do you think should happen by default on failed |
@ilslv I would say not by default. |
I see printing the |
- make `-v` default behavior (no additional output) - make `-vv` additionally output `World` on failed steps - make `-vvv` additionally output docstrings (old behavior) - add `--junit-v` CLI option for `writer::JUnit` Co-authored-by: Kai Ren <tyranron@gmail.com>
Hello,
First of all, thanks for the work on this awesome crate.
If I understand correctly, currently there is no way to disable printing the
World
in error messages. Whenever there is a failed test or panic, the wholeWorld
struct is printed. In some use cases this object can be quite large, making the errors difficult to navigate.Would it be possible to add a command line flag that controls this behaviour?
The text was updated successfully, but these errors were encountered: