Bug in test methodology.

I was running some rollups on the latest Microsoft results (hope to post
those shortly!) and had a discrepancy between what the rollup told me
and what the developers reported.  With test 1235, we swallowed the
response message, so the log only contains a message="1" message.  There
is no message="2".  The assertions against message="2" should fail, but
the way processor-xmlout.xsl works if there is no message, there are no
assertion failures to report.  That's good in the case of testcases
where there are no logs whatsoever, but isn't so good in the case where
one of the messages is simply dropped.

 

I don't know the best way to fix this, perhaps adding in more
assertions, 1235 and in other cases, that check for a given message="1"
that there indeed exists a message="2"?

 

 [  Jonathan Marsh  ][  jmarsh@microsoft.com
<mailto:jmarsh@microsoft.com>   ][  http://spaces.msn.com/auburnmarshes
<http://spaces.msn.com/auburnmarshes>   ]