-- Josh Team <[EMAIL PROTECTED]> wrote (on Friday, 18 April 2008, 08:11 AM -0500): > Off topic but are you guys inferring that ZF has a TestHelper?
tests/TestHelper.php does some behind-the-scenes stuff to ensure that things like include_paths are properly set, test configuration loaded (a number of test suites have optional tests that can be run based on whether or not there are services available, or which need credentials to run), and more. > On Fri, Apr 18, 2008 at 7:51 AM, James Dempster <[EMAIL PROTECTED]> wrote: > > lol and this make me the resistance, aww poop. > > I can't think of any way to solve this problem. I've put my thinking hat > on. > > -- > /James > > > On Fri, Apr 18, 2008 at 1:07 PM, Darby Felton <[EMAIL PROTECTED]> wrote: > > Hi James, > > Yes, the reason I added this line to the TestHelper was for > accommodating the Zend_Session tests, which depend on headers_sent() > returning false prior to their running. > > I did not merge this change to the release-1.5 branch [yet], as I > suspected this change would meet with some resistance (e.g., "why > can't > I see test results as they occur, rather than when they are done?"). > > All things considered, I should probably remove this line from the > TestHelper, and the Zend_Session test suite should be rewritten such > that it does not matter whether output had occurred before the suite > is > run. > > Does anyone else have an opinion on this to share? > > Thanks! > > Best regards, > Darby > > > James Dempster wrote: > > Is there any reason why the unit tests are output buffered? > > -- TestHelper.php #22 -- > /* > * Start output buffering > */ > ob_start(); > > -- > /James > > > > -- Matthew Weier O'Phinney Software Architect | [EMAIL PROTECTED] Zend - The PHP Company | http://www.zend.com/
