Re-Running the last test in VS Code
See original GitHub issueIn our workflow, developers work on the test that’s home in test/component_test.dart
. The file contains a main() method and a root group
, which is further split into N subgroups and tests.
In Android Studio, I am able to hover the main() function, press Control-Shift-R
(I’m on a mac) and all tests in that file run. To re-run the same set of tests, a simple Control-R
is needed.
This is immensely helpful to quickly iterate (until flutter testing gains things like a watcher).
However, this workflow currently seems to be impossible in VS Code. Is that a Dart-Code task (to deeply integrate with VS Code testing framework) or is it something else?
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Keyboard shortcut for debugging the LAST test run in Visual ...
If you are using ReSharper, you can use Ctrl + U , D to rerun ...
Read more >Testing Python in Visual Studio Code
Running the unit test early and often means that you quickly catch ... Test: Rerun Last Run, Debug tests that were executed in...
Read more >Testing Extensions - Visual Studio Code
Visual Studio Code supports running and debugging tests for your extension. These tests will run inside ... Downloads and unzips latest version of...
Read more >Debugging in Visual Studio Code
To bring up the Run and Debug view, select the Run and Debug icon in the Activity Bar on the side of VS...
Read more >Java Testing in Visual Studio Code
Run/Debug test cases ... The Test Runner for Java extension will generate shortcuts (the green play button) on the left side of the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Nothing missed, I think that’s a good point. We can probably have a Re-run Last Test command that works the same, but only tracks tests. I’ll take a look. Thanks!
I some sense not having the rerun last test option destroys a bit my workflow. Example Szenario:
Do I miss something here? How would this be possible with the current version?