CSV Parser fails with invalid XML characters

Bug #570145 reported by edA-qa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
TestPlan
Fix Committed
Medium
Unassigned

Bug Description

If invalid XML characters are encountered they should likely just be omitted. This is likely from a null character.

00000000-00 CHECKPOINT-FAIL Unknown:
        Error: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified.
        Native: <email address hidden>:86
        TestUnit: unit.intr.SetDocumentResponse
AutoStack: in {Unknown}
        Inside call to unit.intr.SetDocumentResponse
        /svn/qa-src-trunk/src/ecm/testplan/auto/seq/otto_uk/ConvertMonitors.test:2: SetParsedResponse text/csv Set.readTextFile %This:Dir%/monitors.csv(/svn/qa-src-trunk/src/ecm/testplan/auto/seq/otto_uk/monitors.csv)("Project ","GroupName","GroupID ","TriggerID","Monitor","Trigger Name"," Day of Sendout ","When to send alert"," Seed email

Related branches

Revision history for this message
edA-qa (eda-qa) wrote :

This was actually cause by an invalid mangled name for the tag name. The generator looked like it wanted to test the first character, but didn't. So it's been fixed. Invalid start characters get prepended with an underscore.

Changed in testplan:
importance: Undecided → Medium
milestone: none → testplan-1-0-r6
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.