Enhanced JUnit Exception Reporting #185
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
|
Awesome! This bug has annoyed me for a while. |
|
How does it behave when a Before hook fails? After hook? Just curious. |
|
If the before hook fails, the scenario is tagged as "failed", steps are tagged as "skipped" If the after hook fails the scenario is tagged as "failed", all steps are tagged as "passed" |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 error reporting (at least in Intellij) had a problem tagging a scenario as failed when a step in this scenario failed (see screenshots).
BeforeFix:
http://rapidshare.com/files/2746712222/JUnitBefore.png
AfterFix:
http://rapidshare.com/files/3491825542/JUnitEnhancedScenarioInformation.png