You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 find 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
@kalvdans thanks for the suggestion! Indeed that would be a nice enhancement and it doesn't look like too much work. I'm a bit overwhelmed by real world these days (hence my late reply) but I'll give it a try once things settle down for me. I'm glad you have a simple workaround in the meantime.
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 find 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=ctest
Would it be possible to make cmake-test-explorer discover a testable directory by the existance of CTestTestfile.cmake?
The text was updated successfully, but these errors were encountered: