Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47194 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87727 invoked from network); 12 Mar 2010 22:18:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Mar 2010 22:18:59 -0000 Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.117 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 63.205.162.117 us-mr1.zend.com Received: from [63.205.162.117] ([63.205.162.117:57015] helo=us-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 57/76-13686-2DDBA9B4 for ; Fri, 12 Mar 2010 17:18:59 -0500 Received: from us-gw1.zend.com (us-ex1.zend.net [192.168.16.5]) by us-mr1.zend.com (Postfix) with ESMTP id 461AF43F81 for ; Fri, 12 Mar 2010 14:20:23 -0800 (PST) Received: from [192.168.16.93] ([192.168.16.93]) by us-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Mar 2010 14:18:55 -0800 Message-ID: <4B9ABDCE.2070904@zend.com> Date: Fri, 12 Mar 2010 14:18:54 -0800 Organization: Zend Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: internals@lists.php.net References: <4B9926E8.4080202@lerdorf.com> <4B997381.1050300@oracle.com> <4B9A14FF.6000703@iki.fi> <4B9A833A.8040402@zend.com> <4B9A848C.3080701@iki.fi> <4B9A93EE.7080403@zend.com> <1418253B-84A3-4CA6-965B-A2501A5D432F@gmail.com> <4B9AB840.1010209@zend.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Mar 2010 22:18:55.0730 (UTC) FILETIME=[012C1520:01CAC232] Subject: Re: [PHP-DEV] Tests repository From: stas@zend.com (Stanislav Malyshev) Hi! > There are going to be some technical challenges. Some (maybe a lot) of test > will need updates or rewriting. run-tests.php may need more improvements > than what is already planned. Knowing this, I would still rather update > run-tests.php and fix the tests, then continue to applying tests to > different branches of the code base. I still have yet to hear *how* these tests are supposed to be updated, to work everywhere. It's very easy to say "oh, we'll just fix them" - but how exactly you're going to fix them if the test is supposed to do one thing in 5.2 and another in 5.3? Are you going to have 2 versions of the file? if(version) wrapping the file? Two sets of output? Check for versions before outputting data? I think it's irresponsible to take such kind of decision without actually seeing what you're going to deal with and how. -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com