-
Notifications
You must be signed in to change notification settings - Fork 152
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
Add Google Test discovery with ctest #2623
base: master
Are you sure you want to change the base?
Conversation
@mweisgut: Do we want to merge? |
@dey4ss : requesting you just in case you have a rough idea of cmake (which is not the case for me) and want to take a look here. If not, I'll go ahead and merge. |
Hey @nikriek, before I merge: I wanted to see the impact on my local machine and how often CMake is reconfigured when I add tests. Surprisingly (to me at least), there was no runtime overhead (I thought there is one given you use a timeout of 30s) and nothing happened when I added a new test to an existing test file (I expected to see CMake being triggered). Is that behaviour expected? Can I somehow see what the effect of this PR is (I don't use any IDE). |
Trying again to ping you, @nikriek. |
1 similar comment
Trying again to ping you, @nikriek. |
During development with VSCode I found it helpful to see and run directly tests from the UI. This PR adds the required test discovery mechanisms for our unit and system tests.