Great! Yes, if there are tests that are more
difficult to write or that change the meaning of the
test, by all means don't change them. But I figured a
few would be easy updates and would allow us to run
more tests using the DOM method.
Guess we also need to implement test filtering (ie.
this test is not valid conf test when using DOM
input/or/output) sooner so we can cleanly run text
output cases.
Yes, I was wondering why we had so few text output
tests - seems like there are a bunch of other tests
that can do wierd output things to text. Plenty of
people do ask about processor output that's not legal
XML.
- Shane
---- you [EMAIL PROTECTED] wrote ----
More comments on test cases:
> lines are from Shane's original message.
>node17 - change to output attrs instead of elements,
so out-of-order
>compares possible
This was changed from plain text to elements, but I
can change
it again.
>select69 - if possible (don't know if it'll affect
test) output attrs
>instead of text, so out-of-order compares possible
I'd prefer to sort by attribute name, but still output
text.
>sort22-25 - can this be changed to xml instead of
text to make wellformed?
>sort30, sort31, sort35, sort37 - can this be changed
to xml instead of
>text to make wellformed?
Yes, but we should probably add more tests that use
the text output
method. So we need to plan on having text-output
compares someplace.
.................David Marston
=====
<eof aka="mailto:[EMAIL PROTECTED]";
humor="Having fun at JavaOne!" />
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
