Change:
constructor(controllerId: string, controllerLabel: string, editors: ExtHostDocumentsAndEditors) { super({ controllerId, <del> getDocumentVersion: (uri: URI) => editors.getDocument(uri)?.version, </del> <ins> getDocumentVersion: uri => uri && editors.getDocument(uri)?.version, </ins> getApiFor: getPrivateApiFor as (impl: TestItemImpl) => ITestItemApi<TestItemImpl>, getChildren: (item) => item.children as ITestChildrenLike<TestItemImpl>, root: new TestItemRootImpl(controllerId, controllerLabel),

Discussion:
<!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.72.0-insider () With the C++ TestMate extension, the hierarchy of test executables and contained tests is no longer displayed correctly. This is a regression that was introduced with . Here's an example. Create a cpp file with the following content: and compile it using taken from . Then, set the config to point to the compiled executable. With VS Code v1.71.0 you get the expected browser content: <img width="581" alt="image" src="https://user-"With the latest Insiders build, or any build from on, you get this instead: <img width="581" alt="image" src="https://user-"Note how T1 is now a sibling of the executable, not a child. Also, the executable no longer has a play button. Cc: to since I'm not entirely sure if this is VS Code's fault, or if there's maybe something wrong with how the extension sets the URIs.
I'm surprised would have anything to do with it, since that only touched decorations in the editor and not the core heirarchy...
Well, I did bisect it to that commit...
Some more information: test rediscovery is completely broken as well since that commit. I'm talking about the situation where you change the config and TestMate reevaluates which executables should show in the browser (I ). In that case, both the old and the new executable are displayed now, both with all their tests. This is reproducible and also started to happen with This is a very serious regression and makes C++ testing a lot harder. At the moment it only affects the Insiders build, but I would hate to see it become a regression in 1.72 if it's not addressed soon. again, I can't tell which of these problems are caused by VS Code or by the extension, so it would help a lot if you could have a look, too.
I'm doing: where : results in: around: I hope it helped
Huh, I'm very confused why that wasn't a compilation error.

Thanks for the hint on the error message...
When will it be this part of the downloadable insider to test it?
<=24 hours after it's merged The bot will ping on this issue when it's ready
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
/verified