Tests are enumerated on test-tab-activation by default?

[Anton-V-K]

I work with Chromium sources, and it seems this extension auto-runs found tests when I switch to Testing tab in VSCode (actuall I use Antigravity IDE), which is very inconvenient, because there are hundreds of tests in Chromium, and it may take hours to pass them all...

I wonder why this feature is enabled by default, so I had to disable it for each workspace?

These are the options I had to add into settings.json for each workspace:

  // Prevent tests from running automatically when modified
  "testMate.cpp.test.autorun": false,

  // Prevent automatic discovery of all tests on startup
  "testMate.cpp.discovery.loadOnStartup": false,

Otherwise IDE and system become almost unusable because the extensions is loading tests...

[matepek]

At tab open the executables are enumerated and executed to acquire the test list, tests are not run.
This enumeration is controlled by: "testMate.cpp.discovery.loadOnStartup": false,

Test-autorun feature is a vscode related option which should not be enabled by default.
If that’s the case it’s a vscode/antigravity issue.
There is no such option "testMate.cpp.test.autorun".

I have to assume your problem is the enumeration.

[Anton-V-K]

Well, that's strange.
Unless I put both mentioned options with false into settings.json, the IDE (VSCode, Cursor, Antigravity IDE) starts executing browser_tests (in some cases even switching to the testing tab isn't needed).
The status bar in this case keeps showing 'C++ TestMate: loading tests...'.
I use Windows 10 64-bit.
All IDEs share same directory with the extensions (specified in %VSCODE_EXTENSIONS%).
The extension version is 4.22.6.

[matepek]

and what is the extension-id?

[matepek]

I cannot even find the autorun word in the source code. 🤷‍♂️

[Anton-V-K]

ID: matepek.vscode-catch2-test-adapter
Here is a fragment from the extension's page (in VSCode):

[matepek]

Based on that you made up a new config variable, you are telling me..

There is an auto run feature but that’s part of vscode, not this extension. I don’t expose that config.