Skip to content
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

Switch to VS Code test runner by default + many fixes/improvements #3574

Merged
merged 19 commits into from
Sep 22, 2021

Conversation

DanTup
Copy link
Member

@DanTup DanTup commented Sep 21, 2021

  • Makes VS Code test runner default
  • Supports showing dynamic tests in tree, with actual results showing as child nodes
  • Live-updates the test explorer tree as document is modified
  • Batches multiple tests being run from the tree/gutter into suites to reduce the number of sessions (and duplicate runs)

TODO:

  • Debounce outline updates since they happen on every change

This fixes #3572, moves some complexity of "phantom groups" and "loading tests" into the package:test adapter (coordinator).

It likely introduces issues with dynamic test names that need fixing.
This will simplify things for dynamic tests that will become containers.
…e times

This could happen using the gutter icons which would send a dynamic test + a node for each of its real test instances, which we'd previously run in a loop. These are now combined into a single regex that includes them all (but won't cause multiple runs).
@DanTup DanTup added is enhancement in testing Relates to test execution of Dart/Flutter tests for end users labels Sep 21, 2021
@DanTup DanTup added this to the v3.27.0 milestone Sep 21, 2021
@DanTup DanTup merged commit c056a71 into master Sep 22, 2021
@DanTup DanTup deleted the default-vs-code-test-runner branch September 22, 2021 10:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in testing Relates to test execution of Dart/Flutter tests for end users is enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant