I created an XSLT Transform and a quick perl script that works fairly well. You can run them from bash as follows:

    xsltproc tl2tr.xslt all_testsuites.xml  | tr "\n" " " | ./transform.pl| xmllint --format - > import.xml

tl2tr.xslt

<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
                xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
  <xsl:for-each select="testsuite">
    <xsl:call-template name="sections" />
  </xsl:for-each>
</xsl:template>
<xsl:template name="sections">
  <xsl:if test="count(testsuite) &gt; 0">
  <sections>
    <xsl:for-each select="testsuite">
      <section>
        <name><xsl:value-of select="@name" /></name>
        <xsl:if test="count(testcase) &gt; 0">
        <cases>
          <xsl:for-each select="testcase">
            <xsl:call-template name="testcase" />
          </xsl:for-each>
        </cases>
        </xsl:if>
        <xsl:call-template name="sections" />
      </section>
    </xsl:for-each>
  </sections>
  </xsl:if>
</xsl:template>
<xsl:template name="testcase">
  <case>
    <title><xsl:value-of select="@name" /></title>
    <type></type>
    <priority></priority>
    <estimate></estimate>
    <milestone></milestone>
    <preconds><xsl:value-of select="summary" /></preconds>
    <steps><xsl:value-of select="steps" /></steps>
    <expected><xsl:value-of select="expectedresults" /></expected>
  </case>
</xsl:template>
</xsl:stylesheet>

transform.pl
while(<>)
{
    # bulleted lists
    s/&lt;li&gt;/\n-/g;
    s/&lt;\/li&gt;//g;

    # kill all html
    s/&lt;\/?[a-z]+( .*?)?&gt;//g;
    print;
}

Hi,

It seems that the new version of testlink (1.9.x) is not supported by your scripts. I think this is because they have changed their system of Steps (we can now create step one by one) so the XML export have changed.

Example of new XML :

<steps>
<step>
    <step_number><![CDATA[1]]></step_number>
    <actions><![CDATA[<p>Ouvrir l'application</p>]]></actions>
    <expectedresults><![CDATA[<p>Arriv&eacute;e sur la page de connexion. Les champs sont vides.</p>]]></expectedresults>
    <execution_type><![CDATA[1]]></execution_type>
</step>

<step>
    <step_number><![CDATA[2]]></step_number>
    <actions><![CDATA[<p>Saisir une chaine dans le champ Identifiant</p>]]></actions>
    <expectedresults><![CDATA[<p>La chaine est saisie dans le champ identifiant.</p>]]></expectedresults>
    <execution_type><![CDATA[1]]></execution_type>
</step>

<step>
    <step_number><![CDATA[3]]></step_number>
    <actions><![CDATA[<p>Saisir une chaine dans le champ Mot de passe</p>]]></actions>
    <expectedresults><![CDATA[<p>Une chaine est saisie dans le champ mot de passe</p>]]></expectedresults>
    <execution_type><![CDATA[1]]></execution_type>
</step>
</steps>

Have you plan to do something to adapt your scripts ?

Thanks by advance.

NB : this new testlink feature is good, it could be a good feature to Testrail

Hello Dennis,

It's not very critical, I just wanted to know if you support these script in the case of we change testlink to testrail.

I try separate testcase steps and it's exactly what I want

Hi Dennis,

As you can !

Thanks by advance.

Hi Dennis...

I am also currently using TestLink 1.9.2 and looking to switch to TestRail, but can only do so once the migration script has been updated to work with the above-mentioned TestLink version.

The script at http://code.gurock.com/p/testrail-migra … 2testrail/ does not work properly - test cases lose their notes, their summaries end up as pre-requisites, and the steps and expected results disappear completely.

If you could please post your updated migration technique for everyone to see, that'd be great!

Thanks,

Dave.

Hello agehl and Dave,

We've now built a conversion script for TestLink 1.9. You can download the updated version from our website here:

http://code.gurock.com/p/testrail-migra … 2testrail/

Please note that you need to configure TestRail for separate test steps, as TestLink 1.9 is also using this format now:

http://docs.gurock.com/testrail-faq/config-steps

Just let me know in case you have any questions or issues with this.

Thanks,
Dennis

It works fine All our projects have been migrated

Thanks a lot Dennis.

Hi Dennis...

Sorry it took me so long to reply, but this just to confirm that the updated migration script worked for me too. Thanks for updating it so swiftly.

Kind regards,

Dave.