You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2015/12/06 11:43:10 UTC

[jira] [Closed] (SUREFIRE-1032) Running junit tests too verbose on command line when parallel execution is false

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

Tibor Digana closed SUREFIRE-1032.
----------------------------------
    Resolution: Later
      Assignee: Tibor Digana

Feel free to reopen it if you are still interested in this issue.

> Running junit tests too verbose on command line when parallel execution is false
> --------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1032
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1032
>             Project: Maven Surefire
>          Issue Type: Improvement
>    Affects Versions: 2.16
>            Reporter: Tom Jenkinson
>            Assignee: Tibor Digana
>
> http://jira.codehaus.org/browse/SUREFIRE-968 changed the output of the surefire plugin such that it is easier to identify the output from parallel executed test suites. Although this design may be appropriate for that use case, it does have negative viewability implications and as such it would be useful to minimize usage of that format where possible. Negatives include: If you are developing on a small window it increases the likelihood of wrapping of the text (if your terminal supports wrapping, or a scroll bar if not).
> For example, if "parallel" execution is not set to true, it would be better to see the old style output.
> I agree it is required behaviour in the context of the use case it was intended to solve.



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