-
Bug
-
Resolution: Fixed
-
P4
-
7-client
-
b03
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2214722 | 8 | Igor Nekrestyanov | P4 | Resolved | Fixed | b12 |
Current set of Junit tests shows several problems:
a) often if one test is failing then execution hangs.
This is mostly because of non daemon threads staying alive
b) some tests fail with NPE as they are not ready to real failure. Need to replace these with asserions.
c) applet-desc in javaws scenario does not complete gracefulle on error as error is thrown in non jubit thread and never delivered to it
d) WebServer need to be shutdown cleanly. Otherwise it will prevent test process from exit.
Make sense to not rely on every test to be robust in this regard
a) often if one test is failing then execution hangs.
This is mostly because of non daemon threads staying alive
b) some tests fail with NPE as they are not ready to real failure. Need to replace these with asserions.
c) applet-desc in javaws scenario does not complete gracefulle on error as error is thrown in non jubit thread and never delivered to it
d) WebServer need to be shutdown cleanly. Otherwise it will prevent test process from exit.
Make sense to not rely on every test to be robust in this regard
- backported by
-
JDK-2214722 Improve robustness of junit tests
-
- Resolved
-