Import Test cases in TL 1.8 XML format

[WT1]

I have noticed with the 1.9beta's that test cases exported from 1.8.5 in the XML format and then imported to 1.9 seem to drop the Steps and expected results sections. I assume this is a bug that will be fixed in the release version. We have a large library of test cases with steps and expected results that we will be importing into different projects.

Can someone confirm the plan is for those to import correctly in the release version?

Thanks

[fman]

xml has been changed due to new steps feature.
There are no provision for supporting older format.

Changes to your exiting XML is following
<steps>
<step>
<step_number><![CDATA[1]]></step_number>
<actions><![CDATA[]]></actions>
<expectedresults><![CDATA[]]></expectedresults>
</step>
</steps>

instead of
<steps>
<![CDATA[
<p>Preset bias to 0</p>
<p>Enable <strong>long range</strong> communications control</p>
<p>Simulate black hole interference</p>]]>
</steps>
<expectedresults>
</expectedresults>

[fman]

These are the search and replace to do (in this order)

------------------------------------------------
FROM: <steps>

TO:
<steps>
<step><step_number>1</step_number><actions>
------------------------------------------------

------------------------------------------------
FROM: </steps>
TO: </actions>
------------------------------------------------

------------------------------------------------
FROM: </expectedresults>
TO:
</expectedresults>
</step>
</steps>
------------------------------------------------

[WT1]

So we will need to do this for every test case in every suite. That is going to be a large effort. Was there a reason for not supporting the 1.8 format for import ? I would guess I am not the only person this will impact badly.

One additional thought, how will this impact upgrading from 1.8 to 1.9. As most of the test cases would already be in 1.8 and when we upgrade should get moved into 1.9 as part of the process upgrading the database. I assume the step and results would be picked up during the upgrade. Is that correct?


Thanks

[fman]

>>So we will need to do this for every test case in every suite. That is going to be a large effort.
You have to do this on each file.
With a tool able to do search and replace on multiple files, this can be done with a low effort

>>Was there a reason for not supporting the 1.8 format for import
Effort to maintain backward compatibilty

>>? I would guess I am not the only person this will impact badly.
no other person has reported

>> One additional thought, how will this impact upgrading from 1.8 to 1.9. As most of the test cases would already be in 1.8 and when we upgrade should get >>moved into 1.9 as part of the process upgrading the database. I assume the step and results would be picked up during the upgrade. Is that correct?
Zero impact because procedure for DB migration between major versions is ALWAYS provided.

[WT1]

Thank you for the information , it was exactly what I needed to know.

[philips2005]

It's Ok with the new format if the user export from TL1.9 and then revise the cases with this format,

[siragone]

Thank you for the informations. But Requirements are missing after the import.
Please can you help me?