[Kolab-devel] How to use the tests that are part of the pear modules?

[Gunnar Wrobel]

Quoting Richard Bos <ml at radoeka.nl>:

> Hi,
>
> I'm making some nice progress to get all the required pear modules for kolab
> available for openSUSE:
> http://download.opensuse.org/repositories/server:/php:/applications/openSUSE_11.1/repodata/
>
> How can I use the tests that are part of the pear modules to verify that the
> packages are build, and have been installed (include their required packages)
> correctly?
>
> E.g.:
> /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/AllTests.php
> /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php
>
> Should one just execute:
> /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/AllTests.php
> and that's it, or are arguments needed and are there any requirements to the
> environment.  E.g. In case of kolab_freebusy is a webserver needed?

On Kolab/OpenPKG you would run the Kolab_Server Unit tests with

  /kolab/bin/php  -f  
/kolab/lib/php/test/Kolab_Server/Horde/Kolab/Server/AllTests.php

for example. This assumes that you have PHPUnit installed and that is  
the only prerequisite. I added this one on the OpenPKG variant because  
I wanted people to be able to run these tests on an installed machine  
in case they modify the code. It makes it easier to check if your  
modifications might create problems.

At the moment there are no higher order tests that would need a  
complete Kolab web server or IMAP server to be setup. The current test  
suites just run in memory and provide some mock drivers for LDAP and  
IMAP. These mock drivers help tremendously during development.

Higher order tests for the Kolab Server are on my todo list though. I  
think we need unit tests that allow to check functionality of complete  
Kolab systems. That would help us during testing the OpenPKG variant.  
An automatic Kolab test suite would of course also make the life  
easier for the native ports as you would be able to quickly check if  
you are up to par with the Kolab OpenPKG system. At least if the test  
suite is big enough.

I am also considering integration of these unit tests into the next  
version of the Kolab web admin. I still need to see if that works out  
as planned. So far I only wrote a minimal amount of code for the new  
web admin (based on Horde 4).

Cheers,

Gunnar

> I did not yet investigate this, I hope that someone can point me in the right
> direction quickly, at least that would be appreciated!
>
> --
> Kind regards,
>
> Richard
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
--------------------------------------------------------------------
    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.kolab.org/pipermail/devel/attachments/20090202/a3f4b396/attachment.sig>