Introduces using doAssert for tests consistently #57
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
Some tests already use doAssert, some use assert. For tests, they should be compileable as debug, release and danger build without losing validity. That makes doAssert the only valid choice.
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 is a tiny PR, just moves the subset of tests that use "assert" from using "assert" to "doAssert"
Some tests already use doAssert, some use assert.
For tests, they should be compileable as debug, release and danger build without losing validity.
That makes doAssert the only valid choice.
I'm currently playing around with solidifying the test-suite (e.g. by adding valgrind checks or similar).
Those PR is somewhat of a prerequisite for that playing around since the test-suite should also be doing tests for -d:danger builds.