Repository navigation
New/renamed/deleted unit test files created externally do not update the Test Runner #5693
Description
Describe the bug
If an external tool (like some AI tool) creates a new unit test file, it does not appear in the Testing tab automatically.
To Reproduce
- Create a new app
flutter create flutter_app_3_35_3 - Open the project folder in VS Code and open the Testing tab to see tests.
- In the integrated Terminal, create a new test file:
touch test/foo_test.dart
Expected behavior
The new test file appears in the Testing tab.
Actual behavior
The new test file does not appear in the Testing tab until you open it in the editor first.
Environment
Operating System and version: macos / Version 15.5 (Build 24F74) darwin-arm64
VS Code version: mac 1.103.2
Dart Code extension: 3.118.1
Flutter extension: 3.118.0
Dart/Flutter SDK version: Dart 3.9.2 / Flutter 3.35.3
Activity
DanTup commentedon Sep 10, 2025
I can't easily test with Claude Code because it doesn't work on Windows (and the watchers are broke in Windows). Can you reproduce this by creating the file from the terminal (for ex.
touch test/foo_test.dart)?Can you also confirm whether the entire file is not appearing in the tree, or the file appears but not the test nodes within it? Thanks!
kinex commentedon Sep 10, 2025
I updated steps to reproduce. The entire file is not appearing in the tree.
kinex commentedon Sep 10, 2025
Related issues: also renaming a test file and deleting a test file (using Terminal) do not work correctly. The Testing tab shows files that do not even exist anymore. Only restarting VS Code / reopening project fixes it.
[-]New unit test file created by an external tool does not appear in Testing tab[/-][+]New/renamed/deleted unit test files created externally do not update the Test Runner[/+]DanTup commentedon Sep 11, 2025
Thanks! I can reproduce this now.
Use watcher for test dicovery to catch modifications outside of VS Code
Use watcher for test dicovery to catch modifications outside of VS Code