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.
When there are skipped tests the test class node (suite in the API) will always be marked as skipped except when tests were aborted. This seems to me rather unexpected because knowing that there are failures is more important. Actually, I would say, that having skipped tests should only be a side note even to passed (but this is less of a problem).
I see even worse case of results handling: I run a test file and there are some passing and some ignored tests (Tests run: 30, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 29.775 sec) and the test class is shown as yellow triangle (warning?) with indecipherable badge and label contains text ABORTED. 1. skipping/ignoring some tests is perfectly OK and those skipped tests should not affect basic red/green status. 2. why was my test run marked as aborted is another complete mystery
(In reply to _ rkubacki from comment #1) > I see even worse case of results handling: > I run a test file and there are some passing and some ignored tests (Tests > run: 30, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 29.775 sec) and > the test class is shown as yellow triangle (warning?) with indecipherable > badge and label contains text ABORTED. > > 1. skipping/ignoring some tests is perfectly OK and those skipped tests > should not affect basic red/green status. > > 2. why was my test run marked as aborted is another complete mystery There were issues in 7.4 with updating the status of the project/testcase status and/or creating the actual nodes. This should be fixed now as this is done asynchronously, fixed in http://hg.netbeans.org/core-main/rev/b9d585b24a9b, so I guess it will take care of the indecipherable badge and label contents. I also agree that errors/failures are more important than skipped tests so will fix this asap.
Changeset: 876539d8b52d Author: Theofanis Oikonomou <theofanis@netbeans.org> Date: 2014-03-03 12:15 Message:
Jirka K., what do you think ?
I agree this should be fixed in 8.0. Unfortunately, internal Hudson does not have any build with the fix. Fanis, where can I verify the fix?
(In reply to Jiri Kovalsky from comment #5) > I agree this should be fixed in 8.0. Unfortunately, internal Hudson does not > have any build with the fix. Fanis, where can I verify the fix? the fix is in core-main and also transplanted to release80: http://hg.netbeans.org/releases/rev/0af97a0d6c69
Integrated into 'releases/release80', will be available in build *201403032200* or newer. Wait for official and publicly available build. Changeset: http://hg.netbeans.org/releases/rev/0af97a0d6c69 User: Theofanis Oikonomou <theofanis@netbeans.org> Log: Task #242311 - Test Results window shows test class skipped when there are also failed tests (transplanted from 876539d8b52da012a498ec935f1df2ce2b894d3b)
Integrated into 'main-silver', will be available in build *201403040001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/876539d8b52d User: Theofanis Oikonomou <theofanis@netbeans.org> Log: Task #242311 - Test Results window shows test class skipped when there are also failed tests
Product Version: NetBeans IDE Dev (Build 201403040001) Java: 1.8.0; Java HotSpot(TM) 64-Bit Server VM 25.0-b69 Runtime: Java(TM) SE Runtime Environment 1.8.0-b129 System: Linux version 3.0.0-12-generic running on amd64; UTF-8; cs_CZ (nb) User directory: /home/cesilko/.netbeans/dev Cache directory: /home/cesilko/.cache/netbeans/dev Verified in the latest development build.