Re: GUI Testing Tools

[Kevin Ryde <user42 zip com au>]

Jeffrey Ratcliffe <jeffrey ratcliffe gmail com> writes:
> put everything that doesn't involve the
> GUI into module(s)

Not necessarily split into modules, but in functions which can be
exercised without too much gui.  Creating some widgets to support
shouldn't be a problem.  Test .t scripts may have to skip themselves if
no DISPLAY though.

> refactoring the GUI code to just call module methods.

Yes, it can make some sense to expose things like a save() method on a
save dialog, being the code which does the real work.

Or go further and make action signals, if you might have do-something
methods which can also run from key bindings.  Could then have
$dialog->signal_emit('save') instead, or in addition.  (Save might be a
bad example, since the "response" signal might be a good place for
that.)