maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1277) Exceptions stacktrace in test are limited to the test class in 2.19
Date Fri, 09 Sep 2016 11:56:20 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15476894#comment-15476894
] 

Tibor Digana commented on SUREFIRE-1277:
----------------------------------------

I only wanted to add a link to the description of the parameter {{trimStackTrace}}
http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#trimStackTrace

So there are two extremes: full stack trace or particular test class.
If you want to keep console clean and see full log for debugging purposes, I recommend to
{{redirectTestOutputToFile}} and download all {{/target}} from CI machine. If you have other
files relevant for your investigation, this may help to reproduce or fix the test.

> Exceptions stacktrace in test are limited to the test class in 2.19 
> --------------------------------------------------------------------
>
>                 Key: SUREFIRE-1277
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1277
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.19, 2.19.1
>         Environment: Windows 10, java 8
>            Reporter: Eric Barboni
>            Assignee: Tibor Digana
>         Attachments: surefiretest.zip
>
>
> Hi,
>  Previous to 2.19, if an execption was raised in tested method the stacktrace contains
trace from the test and tested method. 
>  Now the stacktrace contains only trace from test method, making it complicated to find
the root cause.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message