maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Fabulich (JIRA)" <>
Subject [jira] Updated: (SUREFIRE-446) Surefire fails to capture TestNG results when forkMode=always
Date Wed, 06 Feb 2008 23:23:28 GMT


Dan Fabulich updated SUREFIRE-446:

    Fix Version/s:     (was: 2.4.2)

This is trickier than it looks...  I'm not 100% certain that it even makes sense to run TestNG
with forkMode=always; it isn't necessarily safe to do so (especially when tests depend on
tests in other classes).  [This certainly explains how Benjamin found this bug... ;-)]

Ideally, TestNG would provide its own support for forkMode=always...  Short of that, it's
hard to see how we can hack it into Surefire on top of the framework that's already in place.

> Surefire fails to capture TestNG results when forkMode=always
> -------------------------------------------------------------
>                 Key: SUREFIRE-446
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: process forking
>    Affects Versions: 2.4
>         Environment: Maven 2.0.8, JDK 1.5.0_12, WinXP
>            Reporter: Benjamin Bentmann
>             Fix For: 2.x
>         Attachments: testng-fork-mode-it.patch
> The interplay between {{surefire.Surefire}} and {{testng.TestNGDirectoryTestSuite}} does
not properly notify the ReportManager such that it reports 0 executed tests after the end
of the day. IT to reproduce attached.
> Also confirmed against 2.5-SNAPSHOT.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message