kdelibs (at least) : test building by default
Thiago Macieira
thiago at kde.org
Tue Oct 9 15:07:24 BST 2007
Em Tuesday 09 October 2007 15:36:09 Sebastian Kügler escreveu:
> Well, yes. That should be within the bounds of what's reasonable. For
> example, changing stuff in KConfig should not cause regressions in the
> KConfig unit tests. If other areas are suspicious, it would be nice to have
> them tested as well.
You'd be surprised.
Our policy here in Trolltech is that you should run the tests when modifying
code -- even add new tests for bug fixes. The regressions always come because
you break something totally unrelated.
For example, one fix I applied to QByteArray broke QSettings.
In any case, it's what we can ask. A daily report of breakages should help
with that, including the Last Pass and First Fail revisions.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- 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-core-devel/attachments/20071009/877bae47/attachment.sig>
More information about the kde-core-devel
mailing list