Another approach to GUI testing is to have good logging of the input.

The log should contain all the input such as keyboard and mouse events. It enables the ability to reproduce the state of the GUI by replaying the log file.

When a user finds a bug and submits a log file, it can be used as part of a new test.

Log file GUI tests are less durable than classic perl module tests. When the GUI changes a little, the tests may become useless.

For debugging the appearance of the GUI, the graphics output approach may be required. For debugging the actions triggered by the GUI, a log file approach may be sufficient.

It should work perfectly the first time! - toma

In reply to Re: testing GUIs by toma
in thread testing GUIs by spurperl

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.