Print out full section stacks on failure. #736
Closed
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
The Console reporter now "traces" the full section stack of its current test execution and prints it out instead of the section stack of the failing assertion itself. Likewise, the JUnit reporter now groups assertions together into the <testcase> of the test execution where they happened. This fixes catchorg#734 and allows post-condition tests after the deepest SECTION in a test execution.
|
This looks like what I've been looking for. Thanks! |
justinboneh
approved these changes
Jan 14, 2020
|
Can we revisit this feature? In the case that a segfault happens within a given SECTION, it's useful to know what deepest SECTION was reached to get an idea for where to go looking for the problem. In such a case, I'm not sure how using generators as recommended here would be helpful. |
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 Console reporter now "traces" the full section stack of its
current test execution and prints it out instead of the section
stack of the failing assertion itself. Likewise, the JUnit reporter
now groups assertions together into the testcase element of the test
execution where they happened.
This fixes #734 and allows post-condition tests after the deepest
SECTION in a test execution.