Danny Tuppeny

> This happens if `test` is called after the future returned from main completes. Ah, interesting. One of the failures was `verify_docs_test.dart` in the analyzer, but looking at it now,...

Oh, I see the problem... It's these `test_all.dart` files: ``` main() { defineReflectiveSuite(() { dart.main(); error.main(); file_system.main(); generated.main(); instrumentation.main(); source.main(); src.main(); utilities.main(); verify_diagnostics.main(); verify_docs.main(); verify_tests.main(); }, name: 'analyzer'); } ```...

> With the latest changes I see spamming on the console when I have a single `solo_test` Oh, good spot. I think this is `package:test` behaviour... as part of this...

I agree that changing this in `package:test` would be better. If @jakemac53 doesn't know if there's a strong reason for it to do this (it already indicates skips with numbers),...

Using `dart test` means all of the `test_all.dart` files become redundant. A subtle difference is that the hierarchy added by the calls to `defineReflectiveSuite()` in those files will be lost....

@scheglov interested in your thoughts on the above... is using `dart test` to run tests (instead of `test_all.dart`) reasonable? It does remove the hierarchy that is currently added by the...

@mosuem heh, np - I've been using it lately too on Dart-Code. It's been generally giving me better comments than Copilot and has pointed out a few good bugs. Although...

@connor4312 when you click the CodeLens links here, we call `vscode.TestController.createTestRun()` so I would have expected it to handle this. I'm going to try to fix this up by reading...

@connor4312 actually, I'm a bit confused about this setting... The issue above mentions `OpenExplorerOnTestStart` but that seems to be about opening the Test Explorer, but the bug here is with...

> Before I had mentioned that the Debug Console view sometimes shows inconsistently. To get the screenshot above, I used the green button in the well. It initially showed the...