[
https://issues.apache.org/jira/browse/SUREFIRE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189857#comment-16189857
]
Stig Rohde Døssing commented on SUREFIRE-1226:
----------------------------------------------
[~tibor17] Displaying every stack frame from the test method and up to the
exception seems like a really good solution for errors. Errors are generally
unexpected, so it seems reasonable to assume that users will want to see where
they happened. The current behavior seems good for failures, since assertion
errors are likely either coming from the test code, or from asserts (which then
hopefully have an error message).
I'm not sure what the best place to put the hint is. The most visible would be
in the stack trace where the frames are missing, as in the example in
https://issues.apache.org/jira/browse/SUREFIRE-1226?focusedCommentId=15424904&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15424904.
Putting it in the summary might be fine as well.
> Surefire trims all stack trace elements except those in the test that failed
> ----------------------------------------------------------------------------
>
> Key: SUREFIRE-1226
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1226
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.19
> Reporter: Jiri Locker
> Assignee: Tibor Digana
> Priority: Minor
> Attachments: mvn_stacktrace.tar.gz
>
>
> This looks like a re-occurrence of SUREFIRE-992 but now the stack trace is
> even more trimmed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)