-
Notifications
You must be signed in to change notification settings - Fork 123
Tests take too long to run #2295
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
Comments
As individual test cases are refactored into unit tests, the duration will probably decrease by nil. Only when an entire
|
In addition, just for tracking purposes, as of dartdoc 0.32.2, there were 581 test cases. Converting to unit-test-level tests should encourage more individual tests, with more meaningful failure states. |
Here are some updated stats on my same laptop, at bf7eb56. I'm about to set up a new laptop,
new:
|
Updated numbers:
The unit tests have really dropped! Total time is still 250 seconds, still too long, so this bug remains open. Probably mostly fixed by converting end2end tests. The hard part here I think is the |
This seems obsolete.
|
Currently on my MacBook,
pub run test
takes around 300 seconds. This is far too long. It makes local testing slow, as well as Travis.I suspect most of the waste comes from repeatedly resolving the Dart SDK, for each package in
testing/
, and for each test suite that documents each package intesting/
. The time can be reduced by not resolving so much, or by converting any end-to-end test, which reads real packages fromtesting/
, into a unit test, which uses a mock SDK or mock package graph, etc.It's hard to pick a good acceptance criteria. If work is done to reduce the test duration to below 120 seconds, I think we'd be in a functional state.
The text was updated successfully, but these errors were encountered: