Table of Contents

Bug Triage Day October 25-26th 2008

Who's running it?

(on auto-pilot)

When

October 25th, 26th in #pear-bugs on irc.efnet.org

See http://www.google.com/calendar/embed?src=rslkppoio4rtq6nm7b6fptclfo%40group.calendar.google.com

Attendees

What are we doing

Other items needing volunteers

Notes: The best way to write unit tests for CVS

Say you have a package, Foo_Bar_Item

If you structure you package as:

CVS dir:

/Foo_Bar_Item/

Structure:

/Foo_Bar_Item/Foo/Bar/Item.php
/Foo_Bar_Item/tests/AllTests.php

Then it makes doing

you@locahost:~/pear$ cvs update
you@locahost:~/pear$ cd Foo_Bar_Item
you@locahost:~/pear/Foo_Bar_Item$ phpunit tests/

... work just fine with the existing require_once patterns; and when you install the package, the tests should still run.

Otherwise, if you have packages with different structure, you will often have to:

you@locahost:~/pear$ cvs update
you@locahost:~/pear$ cd Foo_Bar_Item
you@locahost:~/pear/Foo_Bar_Item$ pear package
you@locahost:~/pear/Foo_Bar_Item$ sudo pear install -fa Foo_Bar_Item-0.1.0.tgz
you@locahost:~/pear/Foo_Bar_Item$ phpunit tests/

Unit test results

These unit test results are generated overnight / on demand on doconnor's development copy; so may be somewhat overly passing at the moment :)