I have integrated Test::WWW::Selenium with the pugs smoke test suite to create a graphical output of the tests for our Application. Its bascically these scripts
run-smoke.pl
yaml-harness.pl
testgraph.pl
catalog_tests.pl
I am able to run the tests and the HTML output created but when i click on the Individual test it does not point to the correct test case. This seems to be happening even in the Pugs test output. looking into testgraph.pl the following code
package My::Subtest; use base qw/Test::TAP::Model::Subtest::Visual/; sub link { my $self = shift; my $link = $self->SUPER::link; $link =~ s/\.t(?=#line|$)/.html/; File::Spec->catdir("t_index",$link); }
the $self->SUPER::link is returning a # . The cause seems to be something to do with Test::TAP::Model::Subtest but i am not sure . Any pointers on where the problem could be ?

Thanks to the Pugs team for the modules

In reply to Pugs Smoke test by mkirank

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.