Test file indexing causes slow startup of matlab integration for large projects

[MarcelBrusius]

Describe the bug
Version 1.3.13 added test browser integration.

• Indexing test files launches automatically: starting a matlab terminal takes ages
• Indexing test files cannot be disabled: slows down the overall experience in large projects.
• Indexing test files cannot be aborted
• Test file index seems to be updated even while debugging/running code: debug session cannot be terminated (or it takes longer than I'm willing to be patient)
• Manually set test directories are not persisted: restart of VSCode causes indexing of files in all directories

To Reproduce
Might be only relevant for (very) large projects consisting of more than 1000 files (my project consists of more than 2.5k files)

Expected behavior

• Please add an option to disable the test browser integration.
• Please add an option to save the path to the test folder between VSCode restarts

Screenshots
If applicable, add screenshots to help explain your problem.

Useful Information

• MATLAB Version: R2023b
• OS Version: Windows 11, 10.0.26200 Build 26200
• VS Code Version: VSCodium 1.126.04524 (based on VSCode 1.126.0)

Additional context
In Version 1.3.12 starting a new matlab terminal after connecting to matlab took less than 10 seconds. Now it's in the range of minutes.

[MarcelBrusius]

Some further information:
On a second system, startup of Matlab terminal is significantly faster

• Reason: no test path has been selected

On the initial system, startup is faster again if I go to %APPDATA%/VSCodium/User/workspaceStorage/
There are multiple subfolders for each workspace

• Delet the state.vscdb in the folder corresponding to the workspace that automatically launches test discovery because a folder was (manually) selected at some point
• Note: the workspace.json inside the folder reveals the workspace the folder belongs to

That indicates there's some kind of storage capability already implemented but at the moment it's not possible to revert it easily.

[tsharmaMW]

Thanks for the detailed info and especially for the follow-up investigation. We'll look into improving this in a future update.

• One clarification regarding your request to "save the path to the test folder between VS Code restarts": the test folders and files you select are already persisted across sessions which is why the extension automatically re-discovers tests in those folders after VS Code restarts.

[MarcelBrusius]

You're right, I mentioned it in my last sentence in the comment. There is some persistence already. Though I tried multiple times to remove the tests (or the folders).
But after a restart, discovery started again on its own. So I was locked in and it severely affected the performance to the point I reverted to the previous version.

After finding the mentioned workaround, version 1.3.13 works fine, as long as I don't use the test discovery :)