well, if we can pull it into the codebase or make it optional that is fine.
I just made an update on the blueprint for it, more important need a place to store the tests, and a system for doing the test. Eventually, an automated test system using these, but built into the build system would be ideal. If problem on daily builds, should send emails to the list. Jon On Mon, Jun 13, 2011 at 1:27 AM, Christopher Adams <[email protected]> wrote: > I don't see any purpose to merging the PHPUnit codebase into aiki > core. It's better just to write tests against it and put them in a > tests/ folder. > > We can add our instructions for writing and running tests here: > > http://www.aikiframework.org/wiki/HOWTO_Develop_Aiki_Framework#PHPUnit > > On Mon, Jun 13, 2011 at 2:16 AM, Brylie Oxley <[email protected]> wrote: >> Brylie Oxley has proposed merging >> lp:~aikiframework.admins/aikiframework/PHPUnit into lp:aikiframework. > > _______________________________________________ > Mailing list: https://launchpad.net/~aikiframework.admins > Post to : [email protected] > Unsubscribe : https://launchpad.net/~aikiframework.admins > More help : https://help.launchpad.net/ListHelp > -- Jon Phillips http://rejon.org/ | http://fabricatorz.com/ chat/skype: kidproto | irc: rejon +1.415.830.3884 (global) | +1-510-499-0894 (sf) +86-187-1003-9974 (beijing) _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
