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.