I fixed a jtreg bug a while back when I had a problem with exceptions
in dataProviders. I don't know if it has propagated into the latest promotion.

Roger


changeset:   37:ec890bad20b5
user:        jjg
date:        Tue Jul 09 13:16:13 2013 +0100
description:
7900130: Test summary does not show TestNg dataProvider arguments
7900165: Exception in TestNG DataSource does not result in a reported test failure
7900112: don't print unnecessary stack traces
Summary: Added formatted parameters to test title reporting;
         If a test is skipped due to an exception report it as a failure
         Skip printing of exception if the test result is success
Contributed-By roger.ri...@oracle.com


On 08/14/2013 06:21 AM, Alan Bateman wrote:
On 13/08/2013 14:46, Paul Sandoz wrote:
Hi,

This patch fixes a bug in the data provider of the SpliteratorCollisions.java test, which was attempting to add an element to an unmodifable map.

Interestingly although this caused the data provider to barf, and therefore tests using such a provider were not run, it did not result in jtreg reporting the test-infrastructure failure.

Good catch, I often wonder how often we have cases where a test fails but is reported as passed. Anyway, the change looks fine to me too.

-Alan.

Reply via email to