Better cmake/ctest integration
- Dominant language
- C++
- Stars
- 213
- Forks
- 149
- Avg merge
- 18h 17m
- Merged PRs (30d)
- 2
Description
I started using Boost.Test (again) in a new project. I would like to use cmake/ctest for building and test management. Unfortunately this is not easy possible with 1.74 (debian bullseye). In case it is interesting my current version is in https://gitlab.com/tango-controls/TangoDatabase/-/merge_requests/47. I've followed the https://eb2.co/blog/2015/06/driving-boost.test-with-cmake/.
Current shortcomings:
- The test source code needs to be parsed with cmake to be able to generate a list of tests.This is suboptimal.
- Due to the approach of calling the boost test runner separately for each testcase and excluding all other tests, the JUNIT files are a bit confusing. For three test cases you get three JUNIT files where in each file two test cases are ignored. This would need a flag for boost.Test to skip outputting skipped test cases.
Is there a better approach? Or am I forcing ctest over Boost.Test which is the "wrong" approach?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.