Provide autorun support with the native testing API

[rlivings39]

Checklist

• Checked Support page

After upgrading the extension to a version using the native testing API, I realized that I lost the ability to auto-run Google test C++ tests. The ...->Enable Autorun menu item is not present and a rebuild does not automatically rerun my tests. So for now, I'm switching back to the legacy extension. Am I missing the capability in the new version? If not, creating this feature request to support it.

[matepek]

Yeah, I'm missing that too.
Will take some time.. :/

[stefanhaller]

Yes, this is my only remaining big feature wish too.

However, the way I understand it, it first needs support from VS Code, see microsoft/vscode#134941. While it might also be possible to implement this purely on the extension's side (by extending the context menu for test items), that's not an ideal solution because there wouldn't be a way to visualize which test(s) have auto-run enabled.

[matepek]

Feel free to nudge them on their issue. Let them feel that people care about the feature :)

[H-G-Hristov]

Is this related? Clicking on Refresh in the test panel produces: command 'python.refreshTests' not found

[matepek]

Is this related? Clicking on Refresh in the test panel produces: command 'python.refreshTests' not found

It's not. That button is provided by the python test provider.

[matepek]

connor4312 added this to the February 2022 milestone 11 days ago

🤞🤞

[matepek]

Good news, something is happening in the neighbourhood.
Currently it is scheduled for March.

[Trass3r]

And March it is: https://code.visualstudio.com/updates/v1_77#_finalized-support-for-continuous-test-runs

[matepek]

Will be released in 4.4.0 in hours..

I'm excited and a bit disappointed.
UI currently does not support selection of a set of tests to run continuously just everything.
API does support it and the extension supports it already too. It's only limited by the vscode UI.
One can request vscode developers for the feature.

Anyhow let's celebrate.. its a big day for us.

[Trass3r]

Ok that sounds bad, I wouldn't want to run e.g. long-running integration tests on every change. Though I guess then they shouldn't even be compiled.

I also wonder how it interacts with filtering: microsoft/vscode#173017

[matepek]

microsoft/vscode#178973