Jason Chaffee wrote:
I am pretty familiar with testng code, so I would like to look into this
further. Is it a correct statement to say that the output we are seeing
on the console is coming directly from testng?
No... Console output in Surefire is a bit strange. :-)
By default, Surefire f
, 2008 3:36 PM
To: Maven Developers List
Cc: Maven Users List
Subject: Re: changes to surefire output with testng
Benjamin's links are the right place to start, though I might add that
the
head of that thread is a really long e-mail from me that doesn't
directly
address your question. T
Jason Chaffee wrote:
Hmmm, the bug says it is fixed in 2.4.1 and it still produces a single
suite file and single suite output to the console. I agree with you
Benjamin, I don't think Dan understood the problem and thus didn't
actually fix it. Instead, the fix was for the reporting.
SUREFIRE
-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 12, 2008 3:15 PM
To: Maven Developers List; Maven Users List
Subject: Re: changes to surefire output with testng
Hi,
> Surefire-2.3.1 used to output which test was running and it would
create
> an output fi
Benjamin's links are the right place to start, though I might add that the
head of that thread is a really long e-mail from me that doesn't directly
address your question. The rest of the thread is about your question.
Executive summary: TestNG support was broken in Surefire 2.3.x; it only
wo
Hi,
Surefire-2.3.1 used to output which test was running and it would create
an output file for each test.
I am using testng. Can anyone tell me why this changed and if there is
any way to configure it to behave in the same manner as previous
releases?
Nice to see I am not the only one who i
