You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setup/teardown methods currently show as runnable tests:
This is a little confusing, and trying to run them will fail. VS Code lets us use TestTags to restrict profiles, so we should be able to restrict the Run/Debug profile to "runnable tests" and then only set that tag on runnable tests.
The text was updated successfully, but these errors were encountered:
Might not be related to this change, but after some extension or VSCode update the test results and the Run | Debug buttons are not showing anymore. I suspect the behavior may be related to this change.
@Wdestroier I don't think it's related to this, as those CodeLens links are separate to the test runner integration (they're been around a lot longer than the test runner).
Could you file a new issue about this, and verify whether you can repro it in a newly created project that you could share so I can have the exact same contents? Can you also include the exact version of Dart/Flutter you're using? Thanks!
Setup/teardown methods currently show as runnable tests:
This is a little confusing, and trying to run them will fail. VS Code lets us use TestTags to restrict profiles, so we should be able to restrict the Run/Debug profile to "runnable tests" and then only set that tag on runnable tests.
The text was updated successfully, but these errors were encountered: