Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use a reliable failure mechanism in test enclosure #465

Merged
merged 1 commit into from Mar 25, 2015

Conversation

codemercenary
Copy link
Contributor

assert(false) gets compiled out in release build unit tests, which prevents this case from properly generating a user warning. Switching assert(false) with the googletest macro ASSERT_TRUE() provides more reliability and the added benefit of debug text.

@codemercenary codemercenary force-pushed the fix-enclosureassert branch 3 times, most recently from 45bd833 to 9b7de13 Compare March 25, 2015 21:33
`assert(false)` gets compiled out in release build unit tests, which prevents this case from properly generating a user warning.  Switching `assert(false)` with the googletest macro `ASSERT_TRUE()` provides more reliability and the added benefit of debug text.
gittyupagain pushed a commit that referenced this pull request Mar 25, 2015
Use a reliable failure mechanism in test enclosure
@gittyupagain gittyupagain merged commit 5f015f3 into develop Mar 25, 2015
@gittyupagain gittyupagain deleted the fix-enclosureassert branch March 25, 2015 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants