[Kolab-devel] List of issues for Kolab Server 2.2.3

[Gunnar Wrobel]

Quoting Mathieu Parent <math.parent at gmail.com>:

> Hi,
>
> On Tue, Oct 20, 2009 at 5:34 PM, Thomas Arendsen Hein
> <thomas at intevation.de> wrote:
>> Hi!
>>
>> Here is a preliminary list of issues we want to address in Kolab
>> Server 2.2.3, we aim to make the release in December:
>> ...
>
> Will this release comes from the kolab_2_2_branch? (probably...)
> Current roadmap says "It is planned to have further improvements in a
> release 2.3.0 in the second half of 2009. ", when will be the 2.3.0
> pre-release ?
>
> Also as the team is probably too small to manage feature-based
> releases, wouldn't it be preferable to do time-based releases ?
> I am currently preparing a testsuite for the whole kolab server
> ([testsuite]) that will ease the development process (I hope).
> The script currently does the following :
> - bootstrap a Debian chroot (it is possible to bootstrap other
> systems, see [xen-create-image]) for one master and several slaves
> - launch those virtual machines with VirtualBox or xen (kvm or others
> can be added)
> - create an ssh key to easily controll the vms
> To be done :
> - install Kolab server using native Kolab packages or openPKG
> - run phpunit tests (Kolab_* packages)

The amount of these is going to increase (especially for the Horde 4  
versions of packages). At the same time the nature of these tests will  
slightly change. I had a tendency to write integration level  
(multi-component checks with many assertions) tests in the past. I'll  
keep it more to unit testing (one test - one assertion, for small  
chunks of code) in the future.

> - run other tests : suggestions and patches welcomed!

Nevertheless I also find it attractive to be able to run at least some  
integration level tests over the PHP code. And in principle it should  
not be hard to extend such tests to real world testing the Kolab  
server. On the other hand Bernhard is right: Tests for complex  
situations can be complex to maintain as they often need to be adapted  
with the code. So there is probably a limit there in terms of man  
power available.

If you have suggestions concerning the unit tests suites in the  
Kolab_* packages I'll definitely listen :)

Cheers,

Gunnar



>
> Regards
>
> Mathieu Parent
>
> [testsuite]:  
> http://svn.debian.org/wsvn/pkg-kolab/pkg-kolab_testsuite/testsuite
> [xen-create-image]:
> http://manpages.debian.net/cgi-bin/man.cgi?query=xen-create-image
> INSTALLATION METHODS
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
____ 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 <<
--------------------------------------------------------------------

-------------- 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/20091021/6df14f0c/attachment.sig>