Skip to content

Tests print too much to stdout/stderr #2296

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

Closed
srawlins opened this issue Aug 14, 2020 · 2 comments
Closed

Tests print too much to stdout/stderr #2296

srawlins opened this issue Aug 14, 2020 · 2 comments
Labels
P2 A bug or feature request we're likely to work on type-tech-debt Issues that slow or block desirable development paths for Dartdoc, or create such problems for users

Comments

@srawlins
Copy link
Member

Currently pub run test prints > 2400 lines to stdout/stderr. This makes it hard to follow when one test case fails, as the stack trace can scroll up pretty far.

There are a few places which can reduce this count, something like Package.warn, the print function on the zone, etc. The integration tests may be harder.

I'd say the acceptance criteria can be something like < 500 lines.

@srawlins srawlins added P2 A bug or feature request we're likely to work on type-tech-debt Issues that slow or block desirable development paths for Dartdoc, or create such problems for users labels Aug 14, 2020
@srawlins
Copy link
Member Author

This has been reduced to ~1400 lines 🎉 . Still noisy.

@srawlins
Copy link
Member Author

I got this down to 217 lines of output via test_process. 🎉

Of course 0 is better, but I'm closing this as mission accomplished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 A bug or feature request we're likely to work on type-tech-debt Issues that slow or block desirable development paths for Dartdoc, or create such problems for users
Projects
None yet
Development

No branches or pull requests

1 participant