Something like:

use strict;
use warnings;
use XML::Twig;

my $xmlStr = <<XML;
<doc>
    <testcase1>
    <step1 command ="Launchapp " param1 = "executablepath" param2 = "d
+irpath"/>
    <step2 command = "Dothis"/>
    <step3 command = "Changemode" param1 = "100"/>
    <step4 command = "CaptureRectanlge" param1 = "3" param2 = "96" par
+am3 = "726" param4 = "580"/>
    <step5 command = "CompareImage" image1 = "D:\\img1.jpg" image2 = "
+D:\\img2.jpg "/>
    </testcase1>

    <testcase2>
    <step1 command ="Launchapp " param1 = "executablepath" param2 = "d
+irpath"/>
    <step2 command = "Dothis"/>
    <step3 command = "Changemode" param1 = "100"/>
    <step4 command = "CaptureRectanlge" param1 = "3" param2 = "96" par
+am3 = "726" param4 = "580"/>
    <step5 command = "CompareImage" image1 = "D:\\img1.jpg" image2 = "
+D:\\img2.jpg "/>
    </testcase2>
</doc>
XML


my $twig = new XML::Twig(twig_handlers => {'*' => \&testcase});

$twig->parse($xmlStr);


sub testcase {
    my ($twig, $testcase) = @_;
    my $tag = $testcase->tag();

    return 1 if $tag !~ /^testcase\d+$/;

    print "$tag\n";

    for my $step ($testcase->children()) {
        my $tag = $step->tag();
        my %attrs = %{$step->atts()};
        print "Command: $attrs{'command'}(";
        print join ', ', map {$attrs{$_}} grep {/^param/} sort keys %a
+ttrs;
        print ")\n";
    }

    print "\n";
}

[download]

Prints:

testcase1
Command: Launchapp (executablepath, dirpath)
Command: Dothis()
Command: Changemode(100)
Command: CaptureRectanlge(3, 96, 726, 580)
Command: CompareImage()

testcase2
Command: Launchapp (executablepath, dirpath)
Command: Dothis()
Command: Changemode(100)
Command: CaptureRectanlge(3, 96, 726, 580)
Command: CompareImage()

[download]

This is somewhat messier than it ought be because the test case tags are all different. If the tags were 'testcase' and the case identifier were an attribute the twig_handlers expression could be just 'testcase' and the testing in the handler sub is no longer required.

True laziness is hard work

In reply to Re^5: parse xml and trigger function modules. by GrandFather
in thread parse xml and trigger function modules. by balajinagaraju

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.