First off, I really like what you have done with bringing junit to php. And I REALLY appreciate the example test class you have provided in the more recent version. (And I'm not just saying that to sway you into helping me! ;-)
However, I do have a question. Does anyone out there use this on a large rollout? I'm sure many do, but how do you go about laying out the tests. My php library is broken into many files/many folders and I really don't want to mix the tests with the code. (so that I can use my cvs export to build my qa/prod/other environments.) If you would like a more solid question, how would you set up a test suite for PEAR?
I had tried to develop a layout that mirrored the directories in a parallel folder called tests (or something) but then what? Do I have a filename_test.php for every source module...with all of the feature/bug tests for that module in there. (This worries me for some reason.) Or is there some other alternative that seems to work for larger sites.
Most of my code is tiered, so I'm not worried about checking HTML rendered as much as what comes out of those backend modules. [hmmm] Although, checking the output would be a good future goal. ;-)
Any pointers would certainly be helpful.
- Dan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First off, I really like what you have done with bringing junit to php. And I REALLY appreciate the example test class you have provided in the more recent version. (And I'm not just saying that to sway you into helping me! ;-)
However, I do have a question. Does anyone out there use this on a large rollout? I'm sure many do, but how do you go about laying out the tests. My php library is broken into many files/many folders and I really don't want to mix the tests with the code. (so that I can use my cvs export to build my qa/prod/other environments.) If you would like a more solid question, how would you set up a test suite for PEAR?
I had tried to develop a layout that mirrored the directories in a parallel folder called tests (or something) but then what? Do I have a filename_test.php for every source module...with all of the feature/bug tests for that module in there. (This worries me for some reason.) Or is there some other alternative that seems to work for larger sites.
Most of my code is tiered, so I'm not worried about checking HTML rendered as much as what comes out of those backend modules. [hmmm] Although, checking the output would be a good future goal. ;-)
Any pointers would certainly be helpful.
- Dan