-
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
googletest executables are not showing up in vscode #397
Comments
|
Hello, so I was lucky enough to quickly narrow down what causes this issue. It's very hard to find. It is this line
in the CMakelists.txt which would "Add a test to the project to be run by ctest" https://cmake.org/cmake/help/latest/command/add_test.html In my case ${SRC}=name of the test and ${Test}=executable |
I don't think so. This extension does not parse ctest. |
No it does not depend and it's name was GenericTest, you can see that in the log. |
The test executables build fine with or without the ADD_TEST. |
Then I'm confused. This extension has nothing to do with ctest. |
I'm definitely not using cmake-test-adapter. I had wiped all of vscode and settings from my home dir before carefully installing everything again. |
I still suspect this issue is not test-mate's fault as the log seems to be good. |
The logs above showing that my extension found tests but you still reported them missing. |
It cannot be another extension because in my other independent project it works fine. I can build them at the same time from two separate vscode windows. My workspace settings are also the same. I can run the tests from the cli. They both link same version of gtest. |
I fixed this issue by removing vscode completely including all configuration files from my system and then re-installing. |
Checklist
I understand that you have privacy concerns and I expect you to understand that this extension is developed for free.
Thanks.
Describe the bug
googletest executables are not showing up in vscode
To Reproduce
Tried, but no previous version works at this point so perhaps issue is in vscode.
Logs
The text was updated successfully, but these errors were encountered: