You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2024/05/31 20:31:00 UTC

[jira] [Assigned] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console

     [ https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylwester Lachiewicz reassigned SUREFIRE-1042:
----------------------------------------------

    Assignee:     (was: Tibor Digana)

> Provide way of running tests so that stack trace isn't dumped onto console
> --------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1042
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1042
>             Project: Maven Surefire
>          Issue Type: Improvement
>    Affects Versions: 2.13, 2.14, 2.15, 2.16
>         Environment: Maven 3.x, Linux
>            Reporter: DN
>            Priority: Major
>             Fix For: Backlog
>
>         Attachments: test.zip
>
>
> We never used to get stack traces from any failed tests (asserts) being dumped onto the console. "Upgrading" to 2.16 means that they now get dumped onto the console (UGLY IMHO). Can we at least have the option of the previous output behaviour (2.10 for example)? If there already is a way of achieving this, please advise, I couldn't find anything that had an effect.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)