Build unit tests using Unity instead of CMock #40
Conversation
This file contains 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
yourslab
changed the title
yourslab
force-pushed
the
build/unity-only
branch
from
7a6ee52
to
5be31d0
Compare
aggarw13
reviewed
Sep 29, 2020
…building unit tests
aggarw13
reviewed
Sep 29, 2020
aggarw13
approved these changes
Sep 30, 2020
dan4thewin
approved these changes
Oct 1, 2020
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.
The unit tests in coreJSON have no need for mocks. The CMake files for the unit tests used to reference the Unity submodule in the CMock submodule. Now, the unit test build only references files from the newly created Unity submodule while the CMock submodule is deleted.