elementary-dev-community team mailing list archive
Mailing list archive
We do unit and behavorial testing at where i work, and i think it's great.
Writing tests before you develop the actual feature really makes you think
why your feature should do what and when it should do so.
Maybe we could build vala tests for granite. That would mean we would have
to write tests for existing features too, but when that is done, we can
implement features with first creating a test (a spec) for it, and then
actually implementing it according to the spec. We could then integrate
some kind of continuous integration using something like Travis (if it does
vala), or if launchpad offers that functionality, we can use that.
If it works for granite, we could slowly and steadily move to testing in
all elementary projects.
I think this would in the long term greatly improve stability of the system
and individual apps, will encourage good and maintainable code and
architecture of apps, and it would make elementary developing more
Just my 2 cents...
Op 4 apr. 2013 16:11 schreef "Dane Henson" <dane@xxxxxxxxxxxxxxxx> het
> Here is another practical post I found interesting regarding setting up
> Unit Tests in Vala with Cmake:
> I apologize for spamming the mailing list.
> On Thu, Apr 4, 2013 at 8:56 AM, Sergey "Shnatsel" Davidoff <
> sergey@xxxxxxxxxxxxxxxx> wrote:
>> I strongly recommend anyone interested in automated testing to read
>> through Martin Pitt's Ubuntu Dev Week session on the topic. He's the one
>> responsible for most of unit testing in Ubuntu (he's also the author of
>> Apport which we already use). His IRC nick is "pitti" and the session logs
>> can be found at
>> Sergey "Shnatsel" Davidoff
>> OS architect @ elementary
> Mailing list: https://launchpad.net/~elementary-dev-community
> Post to : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~elementary-dev-community
> More help : https://help.launchpad.net/ListHelp