-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
dart-archive/linter
#4422Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failuresdevexp-linterIssues with the analyzer's support for the linter packageIssues with the analyzer's support for the linter packagelegacy-area-analyzerUse area-devexp instead.Use area-devexp instead.type-code-healthInternal changes to our tools and workflows to make them cleaner, simpler, or more maintainableInternal changes to our tools and workflows to make them cleaner, simpler, or more maintainabletype-test
Description
In anticipation of running tests as part of the SDK build, we need to update them to run using the test discovery mechanism of our test runner.
Today:
dart --enable-asserts \
--disable-analytics \
test/all.dart
(Note the all.dart
vs. discovery of _test.dart
files.)
As a baby-step, updating bot.sh to use dart test
seems good.
As part of this, we'll also want to convert
dart tool/checks/driver.dart
To be run as a test.
SDK migration readiness steps
- migrate
bot.sh
to invoke tests viadart test
- migrate
tool/checks/driver.dart
to a test run in the main test suite
Metadata
Metadata
Assignees
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failuresdevexp-linterIssues with the analyzer's support for the linter packageIssues with the analyzer's support for the linter packagelegacy-area-analyzerUse area-devexp instead.Use area-devexp instead.type-code-healthInternal changes to our tools and workflows to make them cleaner, simpler, or more maintainableInternal changes to our tools and workflows to make them cleaner, simpler, or more maintainabletype-test