Agomezvi

> The reason why it's always running that test is `"program": "${command:cmake.launchTargetPath}",`. Please follow https://github.com/microsoft/vscode-cmake-tools/blob/main/docs/debug-launch.md#debugging-tests @xisui-MSFT Great, this works. But it ignores the "stopAtEntry": true

@xisui-MSFT I have tried the following configuration: ``` { // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit:...

@xisui-MSFT I think I do not understand you. Borja does not have a configuration that works either. Only the configuration that always launches the same test works _**"program": "${command:cmake.launchTargetPath}",**_. Using...

@xisui-MSFT Using _**"program": "${command:cmake.launchTargetPath}"**_ it's able to stop at entry + stop at breakpoints but **the test selected from side panel is ignored**. **Always run the same test,** regardless of...

> Not for me. > > **Same build / target - project, just changing the configuration** > > * Using this config it's able to stop at entry + stop...

Hi @xisui-MSFT @Yingzi1234, sorry for waiting. Using this config throws same issue. No stop at entry, no stop at any breakpoints: ```json { // Use IntelliSense to learn about possible...

@xisui-MSFT Of course here is: [DebugConsole_SingleTest.txt](https://github.com/microsoft/vscode-cmake-tools/files/15271848/DebugConsole_SingleTest.txt)

@gcampbell-msft Yes, it does not solve it

@jophippe Thanks for your input, but it still doesn't work. I think the test properties are correct, anyway I did the “CMake: Reset CMake Tools Extension State” command, but I...