problem with Test (GTest) integration in Test Explorer

[tofDou]

Hello everyone,

With last version of cmake-tools plugin (V1.19.10) and also last rc version of cmake (3.30rc3), my test explorer and test result tabs remains "empty" whereas using CTest in CLI works normally and show me different tests in different test suites.
Naturally I have a worse behavior using the last release of both OSS. Since I noticed very recent bug corrections in CMake and vscode plugin dealing with add_test and extra properties (this commit for instance) and also recent refactoring when discovering tests in vscode plugin, I give it a try...

To be more precise and to give you some inputs:

When I say "empty", the fact is that I have only one item in my tree named as my project name

So I search why the test discovery process "fails"

ctest --show-only=json-v1 --test-dir /home/tof/WorkSpace/BMS_Project/build/Release/src/tests > /tmp/test_list.json

test_list.json

Using the old fashion ctest -N is also OK

ctest -N --test-dir /home/tof/WorkSpace/BMS_Project/build/Release/src/tests

returns:

My hypothesis:

Problem with CTestArgs during the discovery phase???
In my cas without --test-dir option, ctest integration in vscode doesn't work at all since no test where found

more little things...:
extract of settings.json:

{
    "cmake.ctestArgs": [
        "--test-dir",
        "/home/tof/WorkSpace/BMS_Project/build/Release/src/tests"
    ],
    "cmake.ctest.testExplorerIntegrationEnabled": true,
    "cmake.ctest.allowParallelJobs": true,
    "cmake.ctest.parallelJobs": 2,
    "cmake.ctestDefaultArgs": [
        "--output-on-failure"
    ]
}

When switching allowParallelJobs to false , nothings works at all since the ctest command line is completly "broken" with its -R option:

Other Note:
My CTestTestfile.cmake is not in the binaryDir but in a subdirectory build/Release/src/tests/CTestTestfile.cmake.

Same thing for test results

Please help

Any idea to solve this issue for me will be highly appreciated.

[gcampbell-msft]

@tofDou Thanks for all of this testing and information! We primarily follow up with an track issues, so if you could update your issue here: #3842 with all of this context, it would make things easier. I'll follow up with some thoughts and questions in the issue.