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.
Summary: | Unexpected failure in core unit tests | ||
---|---|---|---|
Product: | obsolete | Reporter: | Milan Kubec <mkubec> |
Component: | xtest | Assignee: | issues@obsolete <issues> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | jtulach |
Priority: | P3 | Keywords: | TEST |
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Broken xml file with test failure stack trace.
exc stack trace |
Description
Milan Kubec
2004-10-27 10:10:10 UTC
The test definitively does not parse any XML. The message is produced by xtest infrastructure. The test supplies character (Unicode: 0x2) to assertEquals and XTest cannot parse this invalid XML character in results. Please, fix the test. Created attachment 18565 [details]
Broken xml file with test failure stack trace.
This is a remainder to you, the owner of this bug, that this issue has P3, is reported against 4.0 and its target milestone has not yet been set. Please set the milestone, fix the issue or change its priority by tomorrow. Thank you for helping NetBeans to get ready for code freeze. Fix the test! I can, if really necessary, but only by loosing same information by removing the failure text. I do not like it. It is a bug in xtest that it cannot handle all unicode characters. If we need workaround for now (well, I probably do not), I may replace assertEquals by if (not) fail ("Something is wrong"); but I prefer solution in xtest. OK then. I fixed XMLWriter in XTest to replace invalid xml charactes by its hex value. /cvs/xtest/src/org/netbeans/xtest/util/XMLWriter.java,v <-- XMLWriter.java new revision: 1.7; previous revision: 1.6 It fails again, see attached file. Don't know if it's xtest issue now, please reassign if not. Created attachment 18702 [details]
exc stack trace
Let's leave this closed as the xtest problem is gone. The failure of the testBinaryCacheManager is reported in issue 51025. Verified. |