Re: PEAR-wide unit test suite - Re: [PEAR-DEV] need a few linux/32-64 bits OS testers - Re: [PEAR] [ANNOUNCEMENT] I18N_UnicodeNormalizer-1.0.0RC1
(beta) Released.

On 7/8/07, Christian Weiske <cweiske@cweiske.de> wrote:

#1. Running the test every 12 hours for all packages is probably #overkill. Only, those packages that have changed (new release) #should be tested, including those packages that have not changed but #have dependencies that have changed. That would require my scripts to a) keep package dependency information and b) package release info both which just too hard to implement to just call AllTests.php. Besides that, it takes 15 minutes which is ok.

Getting the full test suite automated is first priority, and then something like CruiseControl can be added to the mix to accomplish this "only run after changes are committed" efficiency boost. -- CRB Let me introduce you to my very own DMCA-protected encryption key: BC 1B 64 4A 8D DE 49 E8 C3 7D CC EE 1A AD EE F5 (compliments of Freedom-to-Tinker http://www.freedom-to-tinker.com/?p=1155)