Re: Integrating extensions with releases

[Sriram Ramkrishna <sri ramkrishna me>]

On Tue, Apr 2, 2013 at 7:42 AM, Emmanuele Bassi <ebassi gmail com> wrote:

hi Colin;

On 2 April 2013 14:37, Colin Walters <walters verbum org> wrote:
> On Tue, 2013-04-02 at 13:07 +0100, Emmanuele Bassi wrote:
>
>> that is going to be massively difficult: we can barely test
>> applications, you want to automatically test a compositor and the
>> combinatorial explosion of 10+ extensions that may or may not conflict
>> between themselves? I doubt you can create an automated system capable
>> of doing that;
>
> We could pretty easily automate basic smoke testing of individual
> extensions.  Given physical hardware:
> https://bugzilla.gnome.org/show_bug.cgi?id=695731

okay, let me amend that: we can easily test that a extension does not
blow up on load. it's a tad harder to check that it actually does not
regress because of UI changes.

I think that it's true that a smoke test will only catch the  failure and frankly that's good enough.  We could get some kind of "test extension" day or something where community could test extensions on the top 20 extensions.

sri

ciao,
 Emmanuele.

--
W: http://www.emmanuelebassi.name
B: http://blogs.gnome.org/ebassi/