[Kde-pim] Unittest policy?

[Ingo Klöcker]

On Saturday 26 September 2009, Torgny Nyblom wrote:
> Hi,
>
> I decided to run the entire kdepimlibs test suite...
>
> This resulted in that after >20 hours I terminated the suite (almost
> all time spent waiting for akonadi tests to timeout) .
>
> I'm wondering if there is a policy about tests in kdepim[libs]?
> Or if there isn't should there be?

The SVN Commit Policy reads

  Test your changes before committing

  Start the application affected by your change and make sure that the
  changed code behaves as desired. 
  Run unit and regression tests, if available (KDE4: make test, KDE3:
  make check).

http://techbase.kde.org/Policies/SVN_Commit_Policy

I haven't found (and I'm not aware of) a special policy for (unit) tests 
in KDE.


> After my test run I think that any tests should always pass and any
> commit that introduces a failure is a bad commit.

Absolutely.


> Further if a test 
> requires any special setup it is that tests responsibility to ensure
> that this setup is in place (in my case the akonadi db tests).

Full ACK.


> $ time make test
> Running tests...
> Start processing tests
> Test project /home/naga/kde/build/trunk/KDE/kdepimlibs
[snipped lots of failed tests]

That doesn't look good.


Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20090926/cf77d0c9/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/