Adding google-test infra-structure. #151
Open
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
This changeset adds the infrastructure needed to run unit tests (google-test). It uses CMake as build system, which makes things simple: Downloads the latest version of google-test and creates the necessary Makefiles for building it correctly. For more infor, refer to README.md
Looking at the Tests/main.cpp I created what would be the unit test for the "SingleVariable" methods. The idea is to extend the tests for all methods already implemented in Tests/main.cpp.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 is the initial implementation for enabling unit testing in this project. I added the infra-structure needed to use google-test and also created a small example of how the tests would look like.
I'd like to get feedbacks on what could be done better (mainly the part that checks for numbers with specific precision...), but I guess the backbone of the feature is handled. I didn't go too deep in the implementation as I don't even know if adding unit tests is going to be approved.
Please let me know if you have any questions, would be a pleasure to answer them :)