Re: Expected test results

Hi there,

You're not looking anymore probably, but I am answering anyway after
over a month. :)

Dethe Elza wrote:
> I've been out of touch with ParsedXML for awhile, but trying to get back 
> up to speed.  I'm running the test suite on a debian system with Zope 
> 2.4 (soon to be 2.5) and a cvs checkout that was updated yesterday.  
> Here's the short form of my results:
> 
> DOM: 1 errors, 11 failures
> ParsedXML: 1 errors, 11 failures
> Parser: 0 errors, 116 failures
> Acquisition: 0 errors, 1 failures

That looks like the normal behavior.

> The error in DOM was a TypeError: attribute-less object (assign or del) 
> in checkChangePrefixUnspecified
> 
> The failures in DOM also revolved around default attributes.
> 
> The ParsedXML error/failures appear to be a mirror of the DOM ones.
> 
> In the Parser I notice two major recurring problems:
> 
> this one:
>   assert wanted == got, \
> 
> and string results being returned as unicode:
> 
>   assert wanted '<?xml version="1.0"?>\n<doc/>\n'[[EOF]]
>   Got: u'<?xml version="1.0"?>\n<doc/>\n'[[EOF]]
> 
> So far, all these issues seem minor and easily resolvable. 

Yes, I did resolve them, but it lead to a crash during the tests...

> The last one 
> is trickier:
> 
> checkParentReferenceIntegrity (test_aqpain.AcquisitionPain)
> Traceback (most recent call last):
>   File 
> "/usr/local/zope/lib/python/Products/ParsedXML/tests/test_aqpain.py", 
> line 43, in checkParentRerferenceIntegrity
>     assert e1a.parentNode.isSameNode(e1b.parentNode), \
> AssertionError: Two references to the same node return different parent 
> nodes.
> 
> OK, so my question is, how much of this is known, expected issues, and 
> how much should I be looking into my environment to fix things?

These are the known expected issues.. I just don't have the time to hunt
them all down and fix them at the moment.

Regards,

Martijn