|
|||
|
I'm having trouble integrating SimpleTest to the MVC framework that Zend uses. What's the best way to structure the unit tests?
Even if I have a folder for "tests", I can't actually access it through my browser due to the clean url's that Zend uses. For example, I can't just have: http://localhost/tests/testfunction without having a TestsController with a testfunctionAction(). Is this the best way to do it? Can someone tell me what is considered "best practice" in terms of FILE STRUCTURE? I realize that I can use a command line approach for SimpleTest, but I was kind of hoping to have a browser-based testing system. Thanks for your time and help! |
|
|||
|
I'm having the same issues, I'm getting lots of dependency issues when I try to require one of my controllers and it then tries to include other stuff...
This site has some info on it but it is for Php Unit not Simpletest.. I've yet to find anything that spells out how to properly setup the structure under Zend. Automatic testing of MVC applications created with Zend Framework | Alex @ Net |
![]() |
| Thread Tools | |
| Display Modes | |
|
|