Testing

Hello, I mean it's to QA, about testing, So far I understand, available pear's test steps are: * PHPUnit for unit tests, what is more function oriented I certainly miss some doc somewhere ? Any package introducing some method should deliver unit tests too ! I mean any new public function should have its own unit test together in package. * pear run-test and the .phpt scripts what is more whole script oriented I sure miss again some documentation... That's the next step in testing and we are quite in real world. (quite= http://marc.theaimsgroup.com/?l=pear-dev&m=110121429907822&w=2 ) These 2 steps should be required for any first acceptance of a release. and augmented for any further extensions. I hope it's no offense if I point out that: (1) I need to edit all of it to build unit or test scripts, I want my box to learn as I'm testing and generate some canvas scripts! Some kind of learning break-points, at begin of scripts or methods, what should be removed by the developer when ok (as debugger) So I can choose afterward what and what tests where meaningfull. (and adapt them by edit for unit or test) I aim to be a good developer, so I must be lazy. (2) The dynamic in the script is not included there What is with two clients asking that stuff tested single in the .phpt script ? Some funny situations can occur. I would believe it's missing some more step, what is related to benchmark (performance oriented) but more to some simulation environment. SIMULATION is the only way to tire the service or to provoke hazard. A third step or layer is missing. Qà+ bertrand Gugger (toggg)