[jbosstools-dev] Re: M2 test failures

[Max Rydahl Andersen]

His point is that random failing tests does not help anything. The green 
bar is not about having a perfect system, it is about verifying that the 
application behaves as it did before you added or changed some 
functionallity.

If you know there is a bug and you don't know how to fix it then write 
the test so it verifies that it behaves as bad as you know it will thus 
when you actually fix the issue (by accident?) the test result will 
change and
you get wiser.

If you got such methods name them as <whateverittests>FailureExpected 
and put some reference to a jira or document the issue in the test.

Then you keep track of it!

/max


Rob Stryker wrote:
> Not to pick on you nick, but that has to be one of the dumbest things 
> I've heard, as a test that can't pass every time could obviously just 
> show a bug that doesn't occur every time.
>
> Nick Boldt wrote:
>> If they can't pass consistently every time, then they need to be: 
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev