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-703) surefire-junit47doesn't work with redirectTestOutputToFile option
Date Tue, 04 Aug 2015 20:44:04 GMT

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

Tibor Digana commented on SUREFIRE-703:
---------------------------------------

[~backuitist]
[~mustaghattack]
Did you try with 2.19-SNAPSHOT or earlier versions?
parallel=classes with forkCount does not make sense, however parallel=methods should work
while forking with junit47 provider.

> surefire-junit47doesn't work with redirectTestOutputToFile option
> -----------------------------------------------------------------
>
>                 Key: SUREFIRE-703
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-703
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.7+ (parallel) support
>    Affects Versions: 2.7.2
>            Reporter: Will May
>            Assignee: Kristian Rosenvold
>             Fix For: 2.9
>
>         Attachments: surefire-junit47-it.patch
>
>
> If you have the redirectTestOutputToFile option set and use the surefire-junit47 provider
(through using the parallel test option or through forcing it), then the output file will
just contain a single newline and so the console logging will be completely lost.
> Attached is an integration test showing this issue which was based off of the fork-consoleOutput
integration test.



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

Mime
View raw message