Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.10.12

Bug #14041 Unpredictable unit test processing sequence
Submitted: 2008-06-01 17:11 UTC
From: akirk Assigned: dufuz
Status: Closed Package: PEAR (version 1.7.2)
PHP Version: 5.2.5 OS: OS X / all
Roadmaps: 1.8.0alpha1    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 50 - 32 = ?

 
 [2008-06-01 17:11 UTC] akirk (Alexander Kirk)
Description: ------------ When doing a recursive "pear run-tests -r" IMO the sequence of execution of test cases is wrong. Only the files within directories are sorted by filename but not the directories themselves. These appear in the sequence they are returned by the operating system. Also, I think that the files within the current directory should be processed first. Expected result: ---------------- $ pear run-tests -r Running 4 tests PASS testcase 1 [testcase1.phpt] PASS dir 1 testcase 1[1/testcase1.phpt] PASS dir 2 testcase 1[2/testcase1.phpt] PASS dir 3 testcase 1[3/testcase1.phpt] TOTAL TIME: 00:00 4 PASSED TESTS 0 SKIPPED TESTS Actual result: -------------- $ pear run-tests -r Running 4 tests PASS dir 2 testcase 1[2/testcase1.phpt] PASS dir 1 testcase 1[1/testcase1.phpt] PASS dir 3 testcase 1[3/testcase1.phpt] PASS testcase 1 [testcase1.phpt] TOTAL TIME: 00:00 4 PASSED TESTS 0 SKIPPED TESTS

Comments

 [2008-06-29 10:43 UTC] dufuz (Helgi Þormar Þorbjörnsson)
I'd say this is a bug, I'll look into it very soon.
 [2008-07-10 22:28 UTC] dufuz (Helgi Þormar Þorbjörnsson)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.