[qmtest] working with the xml result stream

[Stefan Seefeld]

Mark Mitchell wrote:
> On Wed, 2003-10-01 at 06:56, Stefan Seefeld wrote:
> 
>>Mark Mitchell wrote:
>>
>>
>>>Are you willing to work on a patch?  If so, you should make
>>>XMLResultReader._GetResultFromDomNode accept both the old and new format
>>>-- we try to maintain backward compatibility wherever possible.
>>
>>ok, here is a partial patch. It includes the changed document type 
>>definition, and the necessary changes to result.py and 
>>xml_result_stream.py. I didn't include the changes asked for by
>>Nathaniel, as I don't have enough information to know how to generate
>>that reference qmr file.
> 
> 
> I think this patch is a little *too* backwards compatible. :-)
> 
> We don't need for old QMTest to be able to read the new files; only for
> new QMTest to be able to read the old files.  So, there should no longer
> be an "outcome" element.  That means that the "outcome" element
> declaration should be removed from the DTD as well.
> 
> The instructions for Nathaniel's testing regime are buried in
> tests/results_files/QMTest/results_file_database.py.  We should move
> those instructions to README.
> 
> Basically, you want to do:
> 
> /path/to/new/qmtest -D tdb run --result-stream
> xml_result_stream.XMLResultStream
> 
> and then copy results.qmr to xml_results_v3.qmr.

hmm, that writes the xml output to stdout, and the results.qmr
contains pickled data. I assume you meant

qmtest.py -D tdb run --result-stream
xml_result_stream.XMLResultStream > xml_results_v3.qmr

Anyway, that's what I did, and here is the new patch.

Regards,
		Stefan
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch
URL: <http://sourcerytools.com/pipermail/qmtest/attachments/20031001/cd586799/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: xml_results_v3.qmr
URL: <http://sourcerytools.com/pipermail/qmtest/attachments/20031001/cd586799/attachment-0001.ksh>