Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First, it is important to define "test". A test should be an executable that returns 0 if and only if it passes. This is the form of test that CTest understands. The purpose of this PR is to configure the project for CTest tests, introduce a third-party battle-tested unit test framework1, and migrate a few existing tests to that framework.
tests/
directory for holding tests.src/test
still exists, but the intent is to separate, in the filesystem, CTest tests from everything else.tests/
as CTest tests.crypto
module and some tests of thebasics
module totests/
.Footnotes
The unit test framework in this PR is doctest, but I'm not married to it. It is easy to switch among any of the popular frameworks like Catch2 or GoogleTest. ↩