Replace assertions from Caraya with Transparent Assertions#47
Merged
logmanoriginal merged 3 commits intomainfrom Aug 10, 2025
Merged
Replace assertions from Caraya with Transparent Assertions#47logmanoriginal merged 3 commits intomainfrom
logmanoriginal merged 3 commits intomainfrom
Conversation
This replaces the assertions provided by Caraya by my own assertion library Transparent Assertions to get more verbose error messages in the case of failures.
With Transparent Assertions these extensions are no longer needed.
logmanoriginal
changed the title
logmanoriginal
changed the title
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
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 replaces all assertions in the project from Caraya to Transparent Assertions for more verbose error reports.
Caraya is still used as test framework to generate reports and evaluate tests.
Note that Caraya displays the assertion VI instead of the test case because of a limitation in the framework.