[Fwd: Re: [PHP-DEV] Tests - and a question]

From: Date: Mon, 14 May 2007 17:25:42 +0000
Subject: [Fwd: Re: [PHP-DEV] Tests - and a question]
Groups: php.internals 
Request: Send a blank email to internals+get-29414@lists.php.net to get a copy of this message
Somehow I added Jani, but removed internals. Re-sending.. -------- Original Message -------- Subject: Re: [PHP-DEV] Tests - and a question Date: Mon, 14 May 2007 20:55:04 +0400 From: Antony Dovgal <antony@zend.com> To: Zoe Slattery <zoe.slattery@googlemail.com> CC: Jani Taskinen <sniper@iki.fi>, Raghubansh Kumar <kraghuba@in.ibm.com> References: <464891C7.3040806@googlemail.com> Actually I recently proposed to name 64bit tests as *_64bit.phpt and exclude them from the test run on 32bit automatically. Same thing can be done on 64bit - we can exclude *.phpt if *_64bit.phpt exists. That would speed up tests execution a bit. Jani had a different proposal, I didn't recall all the details, so I guess he'll explain it better. On 05/14/2007 08:43 PM, Zoe Slattery wrote:
Hi all We added a few tests for array, string and variable handling functions at the weekend. As always - any feedback will be welcome. One thing we had some difficulty with was keeping the test output small enough to be easily read. We chose to divide up tests like this:
   test_name_b.phpt    b=basic function
   test_name_v.phpt    v=variation
   test_name_e.phpt    e=error cases
   test_name_o.phpt    o=object specific
This may not be the right scheme and I'm happy to change it if anyone has better suggestions, although it is useful to seperate out the error case tests because quite a lot of the differences between php5 and php6 seem to be in the exact form of the error message. Using this doesn't completely solve the problem anyway - I think some of the "v" tests will will end up being test_name_v1, test_name_v2 etc.
-- Wbr, Antony Dovgal

« previous php.internals (#29414) next »