We have a Python project with no compiled code, and no need for cmake. But we still like to use ctest as the test driver. It works fine from the command-line, and have the list of tests in CTestTestfile.cmake (as documented).
In order to get them into vscode test explorer, two hacks are needed to trick cmake-test-explorer to believe the source directory is a build directory:
Create a CMakeCache.txt with a single line: CMAKE_CTEST_COMMAND:INTERNAL=ctest
Brief Issue Summary
We have a Python project with no compiled code, and no need for cmake. But we still like to use ctest as the test driver. It works fine from the command-line, and have the list of tests in CTestTestfile.cmake (as documented).
In order to get them into vscode test explorer, two hacks are needed to trick cmake-test-explorer to believe the source directory is a build directory:
CMAKE_CTEST_COMMAND:INTERNAL=ctestWould it be possible to make vscode-cmake-tools discover a testable directory by the existance of CTestTestfile.cmake?
CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
Migrated from this discussion thread.