next step for testing was Re: GSoC Status Update August/3

[Ian Monroe]

On Mon, Aug 17, 2009 at 8:53 PM, Jeff Mitchell<mitchell at kde.org> wrote:
> Seb Ruiz wrote:
>> 2009/8/18 Ian Monroe <ian.monroe at gmail.com>:
>>> On Mon, Aug 17, 2009 at 3:12 PM, Sven Krohlas<sven at asbest-online.de> wrote:
>>>> So in the end we have a fast test framework with currently
>>>> 18 test classes. Adding more tests is not hard, a guide to
>>>> using and writing Amarok unit tests has just been added our
>>>> wiki. Tell me if anything is unclear there:
>>>>
>>>>  http://amarok.kde.org/wiki/Unit_Testing
>>> I always felt the important thing for this GSoC was that the system
>>> get put into place to start making testing a normal part of Amarok
>>> development. Sven has done the coding side of that (makes sense, it is
>>> GSo*C*), now we need infrastructure.
>>>
>>> We need to have continuous testing so that people can be notified when
>>> their commit caused a test failure. I think making it very clear and
>>> public whats going on with tests will encourage us to maintain and
>>> expand the tests, since it will be quite useful then.
>>>
>>> I can volunteer to help setup a post-update trigger on the server, the
>>> way I did for the commit emails. But thats really an easy part. ;)
>>> Kollide is busy enough already, so we need a volunteer server or
>>> sysadmin I suppose. And then we need some software to run the
>>> continuous testing... if only we knew some guy who worked a company
>>> that did that. :P
>>
>> I'll ask around :)
>
> I can do it. At least for a while. I can give people login/sudo access
> as well, so we're not reliant on just one person to keep it going.

I was hoping you would say that. :D

Ian