kdelibs (at least) : test building by default

André Wöbbeking Woebbeking at kde.org
Sat Oct 6 12:54:01 BST 2007


On Saturday 06 October 2007, David Jarvie wrote:
> On Saturday 06 October 2007 12:13:49 Rafael Fernández López wrote:
> > Hi,
> >
> > On Saturday 06 October 2007 12:41:46 Andreas Hartmetz wrote:
> > > Rafael, did or did I get that wrong?
> > > "But even that is not the point... as Thomas has said on a
> > > message before the important thing is that tests should be ran
> > > for keeping up the quality of the final product (is not a "for
> > > making them compile" only discussion)."
> >
> > Only that if you have changed something that could affect the
> > behavior or something that a test is related to, you should run it
> > (and I didn't mean automatically).
> >
> > Hmm... but probably we could do it even automatically as Olivier
> > suggested... but then comes this problem.
> >
> > What problems has tests without X ? Those that hasn't got GUI
> > should work nice...
>
> And some tests (e.g. in kdepimlibs/kcal) take a very long time to run
> - enough for a couple of cups of coffee. Although there is still the
> option of killing tests if they are taking too long.

Unit tests should be fast otherwise they aren't run (often enough).




More information about the kde-core-devel mailing list