[Kde-pim] Unittest policy?

[Volker Krause]

On Sunday 27 September 2009 14:54:26 Mike Arthur wrote:
> On Sunday 27 September 2009 12:19:06 Volker Krause wrote:
> > > I'd say, that if we have 600+ tests and running them takes 20 hours,
> > > the tests aren't useful anymore. Even if running them takes 10 minutes
> > > you cannot expect developers to run at every check-in.
> > >  I'd say, you should run the tests for the module (sub-directory) you
> > > are working on.
>
> Just out of interest (something that hit me at a job before): how many of
> the tests sleep by a certain amount of time?

I know that there are various sleeps (usually <1s) in the Akonadi tests, when 
waiting for activity of the Akonadi server. Waiting for signals is easy, no 
need for sleeps there, but I haven't found another way to verify that a 
certain signal is not emitted, in a multi-process asynchronous environment.

Note that that's not what makes these tests so slow, that's the complex setup 
(and cleanup) needed to run them.

regards
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20090928/66fcd46b/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/