Skip to content
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

Use Catch for unit tests #3232

Closed
nlohmann opened this issue Dec 30, 2021 · 3 comments
Closed

Use Catch for unit tests #3232

nlohmann opened this issue Dec 30, 2021 · 3 comments

Comments

@nlohmann
Copy link
Owner

The latest Doctest release added a regression with MSVC 2015 (see #3228 and doctest/doctest#573). Furthermore, Doctest is looking for maintainers (doctest/doctest#554) and the future of the project is unclear. Meanwhile, Catch seems to be actively developed.

@philbucher
Copy link

Hi @nlohmann,
did you measure the compilation and runtimes of the two libraries?
I switched from Catch to Doctest for one of my projects some time ago because the compilation times were comparatively large with Catch.
However this was before Catch decided to drop the header-only approach, so not sure how the situation looks currently

just curious, as I am somewhat involved with doctest now :)

@nlohmann
Copy link
Owner Author

This was the same reason for me to switch to Doctest. I don't really want to switch back to Catch, but I was afraid that Doctest somehow stalled as they were looking for maintainers (which seems to have been solved now). I did not compare the compilation times yet - the Catch branch #3236 does not work right now, because Catch triggers several compiler warnings. If the newest Doctest release 2.4.8 works, I will close this issue and hope to not touch the test suite again for a long time :)

@nlohmann
Copy link
Owner Author

nlohmann commented Feb 5, 2022

Closed. Doctest development continues.

@nlohmann nlohmann closed this as completed Feb 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants