[Kolab-devel] php tests

Richard Bos ml at radoeka.nl
Sat Feb 28 11:04:07 CET 2009


Hi Gunnar,

Op woensdag 25 februari 2009 08:28:46 schreef Gunnar Wrobel:
> > Which module is really using this module when tests are executed?  Are
> > e.g. tests in kolab-filter using methods from this Horde_Notification
> > module? I would like to know this to determine which rpm should pull in
> > this package
> > as a dependency.  Or do all kolab-* packages requires this package?
>
> The modules Kolab_Storage, Kolab_FreeBusy, and Kolab_Filter use these  
> new modules for their unit tests. I only added these optional  
> dependencies in Kolab_Filter at the moment (see that package spec).

I have added those dependencies to the respective rpms.

> Currently running the tests on an OpenPKG system yields:

I have attached my results of the tests to this email.  I have attached 
results before and after horde-notification was installed.  Without horde-
notification the results are more like yours.  I have horde-notification from 
the pear.horde.org repository without any patches.

A test fails, because it can find the file:
ls: cannot access 
/srv/www/htdocs/horde/lib/Horde/Kolab/../../../../../config/registry.php: 
No such file or directory
There is a file with such a name present at: 
/srv/www/htdocs/horde/config/registry.php

When I remove ../../ the 'ls <above filename>' works:
/srv/www/htdocs/horde/lib/Horde/Kolab/../../../config/registry.php

To test the failing test I copied the file 
/srv/www/htdocs/horde/config/registry.php to 
/srv/www/htdocs/horde/lib/Horde/Kolab/../../../../../config/registry.php
This results in:
1) testFetch(Horde_Kolab_FreeBusy_FreeBusyTest)
Undefined variable: acl                        
/usr/share/php5/PEAR/Horde/Kolab/FreeBusy/Cache.php:175
/usr/share/php5/PEAR/Horde/Kolab/FreeBusy.php:149      
/usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php:91
/usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/AllTests.php:36    
/usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/AllTests.php:63    

What to do with this warning:
PHP Warning:  Call-time pass-by-reference has been deprecated;
Should I indeed set allow_call_time_pass_reference to true in php.ini as 
suggested by the warning?


> PHPUnit 3.3.3 by Sebastian Bergmann.
>
> ..............
>
> Time: 0 seconds
>
> OK (14 tests, 58 assertions)
> PHPUnit 3.3.3 by Sebastian Bergmann.
>
> .......IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII...................  60 / 121
> .......................................IIIIIIIIIIIIIIIIIIIII 120 / 121
> I
>
> Time: 0 seconds
>
> OK, but incomplete or skipped tests!
> Tests: 121, Assertions: 177, Incomplete: 56.
> PHPUnit 3.3.3 by Sebastian Bergmann.
>
> ...........................F.....
>
> Time: 1 second
>
> There was 1 failure:
>
> 1) testGetImapFailNoServer(Horde_Kolab_Storage_FolderTest)
> Failed asserting that two strings are equal.
> expected string <localhost>
> difference      <xxxxxxxxx???????>
> got string      <imap.example.org>
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:167
>
> FAILURES!
> Tests: 33, Assertions: 197, Failures: 1.
> PHPUnit 3.3.3 by Sebastian Bergmann.
>
> .....................
>
> Time: 2 seconds
>
> OK (21 tests, 44 assertions)
> PHP Warning:  require_once(Horde/Kolab/Test.php): failed to open  
> stream: No such file or directory in  
> /kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on
>   line 17
> PHP Fatal error:  require_once(): Failed opening required  
> 'Horde/Kolab/Test.php' (include_path='.:/kolab/lib/php') in  
> /kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on
>   line 17
> make: *** [test] Fehler 255
>
> Basically 1 failure in Kolab_Storage and some bigger problems in  
> Kolab_FreeBusy.
>
> Kolab_FreeBusy is still on my ToDo-List.

-- 
Richard


-------------- next part --------------
A non-text attachment was scrubbed...
Name: kolab-tests-results.tar.bz2
Type: application/x-bzip-compressed-tar
Size: 2087 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20090228/8b8434e8/attachment.bin>


More information about the devel mailing list