Add first unittest #497
Open
Add first unittest #497
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds an initial unittest against the bitcoinamount module. This is the simplest c++ module to test so its an easy first target. I think the Qt test framework is the best fit for the project and eventually I imagine GMock will be needed to mock out portions of bitcoin interfaces as well as more complex modules get tested. These changes update the CMake definitions and add a BUILD_APP_TESTS option to toggle building of the unittests.
A new ci workflow is added as well to run the unittests (and eventually other testing that we have).