vasuperl:

Your question is a bit too open-ended for me to know how to answer with any detail. For a start, though, I think I'd use something like HTML::Table to generate a summary page to show the test cases and results. Then I'd create separate HTML pages for each test.

What part of your project is giving you trouble?

...roboticus

When your only tool is a hammer, all problems look like your thumb.

So what happened to xml?

There are Perl modules that will assist you in creating HTML; use Super Search here and search CPAN. The details on how these work requires reading on your part. If something isn't clear, some experimentation should resolve it. If not, please post a question here.

my @markup = qw( XML HTML YAML EBML BeerXML );
foreach(@markup) {
    print "How to create $_ file using perl";
}
[download]

### BeerXML

Your request is, at this point, so vague that it it’s clear that you’ve only just begun to consider the problem.   Here are a few pointers to (IMHO) point you in the right direction:

(1)   All of the HTML output should be templated.   Consider Template::Toolkit.   The HTML text is stored in a template-file which specifies, among many other things, substitutions and even conditional logic.   The site “renders” a particular template, passing input-variables to it, and then sends the (HTML ...) result of that render back to the client.

(2)   You will need to devise a URL-structure that will ultimately be used to make “a hyperlink to a particular test-case.”   A common strategy is the so-called “REST-ful URL,” such as http://mysite.com/case/casenumber.   The website is driven by a CGI script (consider using tools like Dancer, Catalyst, or a slew of others ...) which will (among other things) recognize a URL-string /case/... and, from that URL-string, extract and interpret the casenumber argument.   Using that argument (and, having validated it ...) the site will either generate a (templated ...) output-page which describes that case, or a (also templated ...) 404 Not Found response.

(Note: there are complete “content management website” packages in CPAN, too.   This is an extremely-common business requirement which has been thoroughly implemented by other people who were then very willing to share what they had done.   So, there is no reason to “start from scratch.”   Rather, you will (after fully understanding the problem ...) select 90% of the solution you need, then customize 10% to make it “yours.”

Actum Ne Agas:

  Do Not Do A Thing Already Done.™

The place to begin is with reading.   Here, on this site, and with the ubiquitous Google or DuckDuckGo.   Get through the initial learning-curve ... firmly understand what the site must do, then learn how to do that using a particular tool (Perl-plus-CPAN-packages).   A good, solid week’s-worth of online research, as the next thing to do, will do you very well.   Feel free to ask here with other questions, especially after you have done this.