-
Notifications
You must be signed in to change notification settings - Fork 215
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
Output lines are messed up with several tests files #86
Comments
Seems to be similar to google/grinder.dart#194 I run into when I run tests using Grinder. |
The runner runs multiple test suites in parallel. This means that there's not a clear linear progression of tests, since multiple tests are running at once and they may overlap, so it has to decide what to print when. The heuristic it uses is simple: it always prints the name of the test that's been running for the longest. This means that quick tests may not show up, and slow tests may show up for longer, but it also produces the least incomprehensible flickering on the command line.
Single-line output works via the magic of the carriage return or Unfortunately, there's no way (short of C APIs that are inaccessible to Dart) to determine the actual width of the terminal, so we have to just choose a number. The best workaround is to widen your terminal. |
Thanks for the explanation. |
Actually, this may not be true; it looks like most Unix terminals are capable of more advanced manipulation just using escape codes on standard IO. That's worth investigating in the future. |
Actually, |
Unfortunately, this is blocked on |
Is there any update on this? Is it still blocked? |
No, this is no longer blocked. |
Fall back on a 200-character default, which is less likely to obscure test names when printing to a non-terminal destination. Closes #86
Use Stdout.terminalColumns for line length Fall back on a 200-character default, which is less likely to obscure test names when printing to a non-terminal destination. Closes #86
When I use
pub run test
(with test-0.12.0-beta.10 and Dart 1.10.0-dev.1.9) when several test files are available, the output lines seem not correct (dupplicated or removed).For instance with the rational package:
BTW: I don't really know why but depending on the screen size the
pub run test
output is either a single line or the above multi-line output. What is the reason ?The text was updated successfully, but these errors were encountered: