kdelibs (at least) : test building by default

[Thomas Zander]

On Saturday 06 October 2007 11:49:50 Andreas Pakulat wrote:
> > In the KDE as well as all of the software world unit tests should be
> > part of life.  Just like you compile before you commit, you should
> > run the tests to see if you introduced a regression.
>
> That would need however a way of communicating which tests worked and
> failed before my changes, else I have to build 2 versions of the same
> module and compare which I seriously doubt many people would do
> (personally I wouldn't do that either). I'm not sure where to put that
> information though.

I'm not sure how many tests fail; but I expect we can fix this by adding a 
QSKIP macro, for example.  That issue really is something that can be 
fixed (and should be fixed) but has little effect on the change of the 
default as proposed in this thread, doesn't it?

-- 
Thomas Zander
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071006/e9c9517c/attachment.sig>