summer of code: Code regression test suite, implemented with QtScript

[Igor Trindade Oliveira]

On Sunday 01 March 2009 17:49:36 Ian Monroe wrote:
> On Sun, Mar 1, 2009 at 2:04 PM, Igor Trindade Oliveira
>
> <igor_trindade at yahoo.com.br> wrote:
> > On Sunday 01 March 2009 14:28:36 Ian Monroe wrote:
> >> On Sun, Mar 1, 2009 at 11:16 AM, Igor Trindade Oliveira
> >>
> >> <igor_trindade at yahoo.com.br> wrote:
> >> > Hello,
> >> >
> >> > My name is Igor Trindade and i was talking about Mark Kretschmann
> >> > in IRC and he suggest me send a email to this list talking about my
> >> > idea for this project and about me.
> >>
> >> I'm moving this to amarok at kde.org since thats where we're talking to
> >> students (despite what Mark might have said :D).
> >>
> >> > the project.
> >> >
> >> > The project would be divided in two parts. The first one is port
> >> > akonaditest to use amarok(can be done in two weeks), akonaditest
> >> > basically create a new environment so ,for example when run tests the
> >> > developer data does not stay compromised( i am akonaditest author).
> >> > the second part is write the regression test and the unit test library
> >> > for Amarok and integrate it with CMake.
> >>
> >> I love that you already have experience with testing since we have no
> >> experience. :) Amarok has one unit test in trunk... and it doesn't
> >> work.
> >>
> >> Is there something akonadi-specific about akonaditest currently
> >> (outside of its name?) Maybe perhaps instead of "porting to Amarok"
> >> you could make it generally useful for Qt applications (or is it
> >> already?) As you can tell, I don't know much about akonaditest. Since
> >> the KDE community as a whole decides which projects are accepted, its
> >> better if you can make clear that your project assists the broader KDE
> >> community (only if that makes sense of course).
> >
> > right now akonaditest just works with Akonadi but  can easy ported to
> > others frameworks and applications.
>
> Looking at the akonaditest wiki page, it sets up a test environment
> and then runs a bunch of tests. So for Amarok it would setup a test
> database and run unit tests I suppose.
>
> So perhaps instead of porting it to Amarok, you could use a plugin
> interface to support both akonadi and amarok? I'm not familiar with
> the code at all so I don't know if this actually makes sense.
Yes,
In in fact after port it to works to Amarok, it can be ported to work with 
kwallet for example(just writing a plugin).
Would be very simple make it.
>
> Ian
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok