Hello Jared, this is the first prodictive mail in this thread, we can easily extend the .phpt system to have different expectations for different versions of php. That was we can handle stuff that slightly changes like spell correction in error messages and such.
Now not to you Jared but to all: <[EMAIL PROTECTED]> However i said that already on IRC nobody is taking care on tests but complain is what you guys are all goo at! Instead of screaming and whining after a release you should write tests. When looking at <50% coverage from a test run and @ <5K tests for a beast as big as php that's a joke. So what to expect? Things change at will becuase we have nothing to test against until somebody screams after a release.... </[EMAIL PROTECTED]> best regards marcus Thursday, May 11, 2006, 2:58:04 PM, you wrote: >> Pierre wrote: >> > I forgot to mention how vicious such changes can be. Most >> of times the >> > related tests are "updated" in the same commit (or right after) to >> > follow the new behavior. Making nearly impossible to know about the >> > breakages without duplicating core tests in our apps. Also commit >> > messages or changelog entries are rarely explicit enough to mention >> > them. >> >> Maybe we could set up a testing system that runs the tests >> from PHP_4_4, PHP_5_0, PHP_5_1, and HEAD and shows the >> differences? That way we would notice that a test that >> passed with a previous version fails with a newer one. > Would have to diff the various tests too. > Perhaps the tests cases should never be removed, but the expected results > altered so a diff between differing test suite versions > can show what behaviour has changed. > Jared Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
