This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
It would be very nice to have state "failed by bug" and it's support (corresponding methods) to have possibility to mark some testcases which failed by known bug.
Why to have state fail by bug? You can specify it in: 1) message assertTrue(condition,"see to #85688 defect) 2) test case name testRegression85688() { }
Yes, these 2 cases are possible but not convenient. But in case if we have special state 'failed by bug' then we can easy select such kind of bugs. Also it helps to identify which tests need it's owner review and maybe some update.
We discussed this issue with Alexei Mokeev in July 2005 but we couldn't agree on it. My opinion is that 'expected fail' status is enough. My use case: - a test case fails - test's owner files a bug for it - now one can use a or b a) - the test case is failing until the bug is fixed - test starts to pass when the bug is fixed b) - test's owner marks the test case as 'expected fail' in cfg - test will finish with result 'unexpected pass' when the bug is fixed - test's owner remove 'expected fail' attribute from cfg
Implemented by Andrey and merged to trunk: http://xtest.netbeans.org/source/browse/xtest/nbjunit/manifest.mf?r1=1.20&r2=1.21 http://xtest.netbeans.org/source/browse/xtest/nbjunit/src/org/netbeans/junit/NbTestCase.java?r1=1.59&r2=1.60 http://xtest.netbeans.org/source/browse/xtest/nbjunit/src/org/netbeans/junit/AssertionKnownBugError.java?rev=1.2&content-type=text/vnd.viewcvs-markup http://xtest.netbeans.org/source/browse/xtest/src/org/netbeans/xtest/testrunner/XMLReporter.java?r1=1.17&r2=1.18
Verified.