Created in-house assert testing functions for better propagating source method/type of assertion failures #6
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.
A large number of the tests in this project are setup in a format like follows:
Prior to this change, assertions wouldn't notate which passed type caused the test failure. Now, using the new assertion functions
CTAssertTrue,CTAssertFalse,CTAssertEqualpropagates the name of the method that called it as well type it compares (forCTAssertEqual) for better visibility into the function, and more specifically, the type caused a particular test failure.