Repository navigation
Test icon change on new run doesn't happen on test_reflective_loader that is not from context menu #5928
Description
Describe the bug
After #5904 we should always see gutter icons changing when a new debug session starts, but that is not always the case.
It does work if you use the context menu options from the gutter icon and from the Testing sidebar.
To Reproduce
Steps to reproduce the behavior:
- Open
pkg/analysis_server/test/src/services/correction/fix/add_static_test.dartin Dart SDK - Run the file with F5
- Add a breakpoint on line 23
- Run the file with F5 again or by using the code lenses
- See the other icons did not update
Expected behavior
For the icons representing the other tests to update.
Screenshots
Please complete the following information:
Workspace Environment
Dart Code extension: 3.129.20260224
Flutter extension: 3.129.20260202 (activated)
App: Visual Studio Code
App Host: desktop
Version: win 1.109.5
Workspace type: Dart (LSP) (Multiroot)
Workspace name: sdk (Workspace)
Dart (3.12.0-edge.265b75c74e46e1a6a1543f261633d92e264082e1): C:\Users\felip_0vh5fa6\dart
Flutter (3.38.7): C:\Users\felip_0vh5fa6\.puro\envs\stable\flutter (No device)
Output from 'dart info'
C:\Users\felip_0vh5fa6\dart\bin\dart.exe info
If providing this information as part of reporting a bug, please review the information
below to ensure it only contains things you're comfortable posting publicly.
General info
- Dart 3.12.0-edge.265b75c74e46e1a6a1543f261633d92e264082e1 (main) (Mon Feb 23 08:49:29 2026 -0800) on "windows_x64"
- on windows / "Windows 11 Pro" 10.0 (Build 26200)
- locale is pt-BR
Process info
| Memory | CPU | Elapsed time | Command line |
|---|---|---|---|
| 0 MB | -- | dart.exe | |
| 0 MB | -- | dart.exe | |
| 0 MB | -- | dart.exe | |
| 0 MB | -- | dart.exe | |
| 0 MB | -- | dart.exe | |
| 0 MB | -- | dart.exe | |
| 0 MB | -- | dart.exe | |
| 0 MB | -- | dartvm.exe |
Activity
DanTup commentedon Feb 25, 2026
I can repro.
We only queue the tests when the run is triggered through something that we know the test nodes for. When you press
F5we don't have the test nodes, we just run the entire file and then collected nodes from the output.I'm not sure if we can reliably know which tests will run this way (for example you might have added a
@soloTest). But perhaps we could at least mark the suite as queued (so its icon would change), it would at least give some more info.Alternatively we could mark all tests in the suite as queued, but that would be misleading if some tests were not going to run. I'll try them out and see how they look.
FMorschel commentedon Feb 25, 2026
If you dislike your options, we could always simply hide/delete those, right? Since they will be captured again anyway.
Mark suites as queued when run outside of the test runner
DanTup commentedon Feb 25, 2026
I'm going with this for now. The skipped tests still send
testDoneevents, so they will change from queued to skipped as they are processed, and at the end of the run any remaining queued tests are reverted anyway. It's possible running from the test runner has this issue anyway (eg. mark a test as skipped, then use the test runner to run the parent node.. it'll still get marked as queued initially).Don't enqueue() entire test suite unless we know the whole suite is b…