-
Notifications
You must be signed in to change notification settings - Fork 27.1k
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
Test output is hard to read #27845
Comments
I'm starting to think that it might not be entirely reasonable to solve this in a single way. It would probably be easier to just make a new reporter for test ( |
Compared to Eg no ability to add custom arguments to add new behaviour or halt on first test failure for example.
This is our sad solution to run our test suite and only report on errors, when you have a large test suite you really do not care to see passing tests (a dot "." is sufficient) it just becomes a chore everytime to scroll up and hunt for when "-1" first occurred to get to the first fail. |
Latest versions have a
I'll add a |
It looks like I've sent #148739 to accept the same argument in Once that's in, @dnfield would you like to enable that option in CI? Are there other changes you'd want to see, either as blockers for using |
And #148739 is now merged, so @andrewkolos has already filed #149611 to consider using it in CI for tests of the |
The
compact
reporter isn't really compact if you have errors, info messages, or skips in your test run. It's particularly difficult if there are multiple failures, or if you're using CI and the failures don't happen to be the very last tests that are run.I have started work on addressing this: master...dnfield:test_reporter but want to solicit feedback. Some things I can think of that we want to acheive:
flutter test
at the moment.json
reporter. We could write our own reporter, but ultimately I'd like to see us able to use the data from our test runs in a more structured manner for analytics, which will probably require wrapping the JSON reporter anyway./cc @jonahwilliams
The text was updated successfully, but these errors were encountered: