gtg-contributors team mailing list archive

[Jonathan Lange <jml@xxxxxxxxx>]

On Mon, Aug 2, 2010 at 5:36 PM, Luca Invernizzi <invernizzi.l@xxxxxxxxx> wrote:
> On Mon, Aug 2, 2010 at 6:31 PM, Bryce Harrington <bryce@xxxxxxxxxxxxx> wrote:
>> On Fri, Jun 11, 2010 at 05:17:55PM +0200, Luca Invernizzi wrote:
>>> FYI, if you want to automatically run tests on commit, give this plugin a shot:
>>> http://doc.bazaar.canonical.com/plugins/en/testrunner-plugin.html
>>
>> Hi, I notice we've got some tests for backend functionality, but should
>> we write tests for browser UI functionality?
>
> Eh, the problem is: how? The only toolkit I'm aware of is Mago, and
> writing a test seems quite complex. Anyway, the Gedit people have done
> that, so maybe it's doable. We have discussed this topic at GUADEC,
> and the most viable solution seemed to keep the UI part untested and
> as thin as possible.

Actually, for a lot of stuff you can do productive testing by making
direct calls to GTK elements and then checking the value of attributes
of UI elements.

I've done it once in a smallish project to great benefit.

jml