Created attachment 165020 [details]
TestNg with dataprovider

Many things are not consistent in this verry little tryout of TestNG and it's @Dataprovider capabilities.

The test sources codes and 2 screenshots are attached.

the (stupid) test case is a digest oy my initial goal.
It builds a static dataset of pictures and their attributes,
and do some validations.

I noticed weird behaviours. (Green bar while the output status is that some tests FAILED ??)
Thought I was doing something wrong. 
Loose a couple of hours on this , eventually reaching the TestNG index.html in my /AppData/Local/Temp/.

So I ended up with the simple test attached, using an  Assert.assertTrue(currentBool);
the boolean coming from an getRandomBoolean() method.

As what is seems :
1st Defect :
-----------
 if the first test in the suite initiated via an dataprovider is OK, Whatever comes next the bar will be green ! 
Plus some other heuristics I didn't get.. @ some point the current netbeans' module code just don't take in account the fact that in a suite all tests must be OK before you can set the global status to PASSED. (and disrespect the TestNG's output)

2nd defect :
------------
Complete INCOHERENCE in the label :
"NO test passed, 1 test failed " ??? there was 9 tests, 4 passed.
the run after , thanks to the assertTrue based on  getRandomBoolean()'s value
Netbeans claims that "THE" test passed : there was not just a sole unique test. Do you mean "the SUITE" passed ?? (All this not caring about the fact that it failed in the 1st place)