For checking NS renders, I dont see how automating would really help, as you have have a human there to make a subjective decision. Surely automating it would take longer than the QA dept trawling thru' a few web screens (depending on the size of the app).

If your html engine is centralised (ie all the html code gen passes thru' the one spot), I would be inclinded to take a sample of perhaps 10 different web pages (or a significant sample) and verify those.

You can then present your UAT doc to mgmt. If mgmt are particularly anal about these things, I reckon including a disclaimer such as "All HTML is produced via a centralised HTML engine."

If you have a large site, you'll be getting into the land diminishing returns which is obviously just not efficient.

I personally think you would be after a process template, rather than automating a point and click solution. With the process template, you'd have a bit of doco that has all the tests you require, all you have to do is perform the tests on "the next platform" and put the results in your document (word templates work well for me).

In reply to Re: Control the Web browser from the client-side? by Ryszard
in thread Control the Web browser from the client-side? by Maestro_007

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.