-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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 deprecation warning in ParseAndCatchTests #2120
Add deprecation warning in ParseAndCatchTests #2120
Conversation
Codecov Report
@@ Coverage Diff @@
## v2.x #2120 +/- ##
=======================================
Coverage 88.79% 88.79%
=======================================
Files 138 138
Lines 5683 5683
=======================================
Hits 5046 5046
Misses 637 637 |
This should also be explicitly written in the cmake integration docs. |
@horenmar Do we need to document this also in the deprecations information or should that only contain changes in Catch directly and not in the CMake integration? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thx
@norbertwenzel It should be there as well. |
Ok, I think I have everything covered in the documentation now. Let me know should there be something missing still. |
lgtm. Autorebase and the PR is ready to be merged. |
7b2ff07
to
a95a5ff
Compare
Parsing C++ with regex in CMake is error prone and regularly leads to silently dropped (not run) test cases. Going forward the function `catch_discover_tests` from `contrib/CMake.cmake` should be used. For more information see catchorg#2092 (comment)
a95a5ff
to
0107383
Compare
@norbertwenzel did squash the commits, now rebased on current |
Parsing C++ with regex in CMake is error prone and regularly leads to silently
dropped (not run) test cases.
Going forward the function
catch_discover_tests
fromcontrib/CMake.cmake
should be used.
For more information see #2092 (comment)