Skip to content

feat(test): exclude test files from the optimized bundle - #1726

Open
marcossevilla wants to merge 3 commits into
mainfrom
session/dramatic-oriole-kg0j
Open

feat(test): exclude test files from the optimized bundle#1726
marcossevilla wants to merge 3 commits into
mainfrom
session/dramatic-oriole-kg0j

Conversation

@marcossevilla

@marcossevilla marcossevilla commented Sep 9, 2026

Copy link
Copy Markdown
Member

Adds optimization.exclude to the test and dart.test sections of
very_good.yaml, plus a repeatable --exclude-optimization option on
very_good test and very_good dart test. Matching test files are left out
of the generated .test_optimizer.dart and handed to the test runner as
their own targets, which also restores file-level @Tags handling for them.

optimization now accepts a map with enabled and exclude. The previous
boolean form is shorthand for enabled, so optimization: false keeps
working.

The optimized entrypoint is no longer passed to the runner once every test
has been excluded from it, unless there is nothing else left to run.

Closes #1713

@marcossevilla
marcossevilla requested a review from a team as a code owner September 9, 2026 13:10
@marcossevilla
marcossevilla marked this pull request as draft September 9, 2026 15:54
@marcossevilla marcossevilla mentioned this pull request Sep 10, 2026
2 tasks
@marcossevilla
marcossevilla marked this pull request as ready for review September 10, 2026 14:57
erickzanardo
erickzanardo previously approved these changes Sep 10, 2026
ryzizub
ryzizub previously approved these changes Sep 10, 2026

@ryzizub ryzizub left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

marcossevilla and others added 3 commits September 10, 2026 17:41
Adds `optimization.exclude` to the `test` and `dart.test` sections of
`very_good.yaml`, plus a repeatable `--exclude-optimization` option on
`very_good test` and `very_good dart test`. Matching test files are left out
of the generated `.test_optimizer.dart` and handed to the test runner as
their own targets, which also restores file-level `@Tags` handling for them.

`optimization` now accepts a map with `enabled` and `exclude`. The previous
boolean form is shorthand for `enabled`, so `optimization: false` keeps
working.

The optimized entrypoint is no longer passed to the runner once every test
has been excluded from it, unless there is nothing else left to run.

Closes #1713

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@marcossevilla
marcossevilla dismissed stale reviews from ryzizub and erickzanardo via 16b19a6 September 10, 2026 15:58
@marcossevilla
marcossevilla force-pushed the session/dramatic-oriole-kg0j branch from 64d6601 to 16b19a6 Compare September 10, 2026 15:58
@marcossevilla
marcossevilla added this pull request to stack #1730 September 10, 2026 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(test): allow excluding files from optimized bundles in very_good.yaml

3 participants