On Tue, May 15, 2007 12:38 pm, Antony Dovgal wrote:
> On 05/15/2007 08:52 PM, Stanislav Malyshev wrote:
> Well, I'm pretty sure regular humans know how to run `find . -name
> "*.phpt" | xargs grep "func`.
I dunno...
It took me years to figure out that xargs thing and how to make it go...
I'd rea
Hello Raghubansh,
if such a mapping becomes more important i'd say we go with a xml file
mapping maintained in either php-src or phpdoc cvs module. That way we do
not have to rename all files and loose history.
best regards
marcus
Wednesday, May 16, 2007, 1:58:42 PM, you wrote:
> Hello Zoe,
>
Hello Zoe,
It would be nice thing to have mapping between categorization of the
functions in the php doc and the source/test tree structure but keeping the
tree structure as per the source code is better thing to do. If i have got
it right as of now the testcases are places based on the location o
Stanislav Malyshev wrote:
I think it does. If one needs to see which tests there are or are
there any tests that test particular thing or inspect certain aspects
of a functionality, navigating a maze of func_01234.phpt, all alike,
is a nightmare. Of course, I could open all of them one by one a
On 05/15/2007 08:52 PM, Stanislav Malyshev wrote:
That said, I'm happy with both func_b.phpt and func_basic.phpt (and even
009.phpt) =)
We just need more tests, doesn't matter what their names look like.
I think it does. If one needs to see which tests there are or are there
any tests that te
That said, I'm happy with both func_b.phpt and func_basic.phpt (and even
009.phpt) =)
We just need more tests, doesn't matter what their names look like.
I think it does. If one needs to see which tests there are or are there
any tests that test particular thing or inspect certain aspects of a
Hello Zoe,
it ignores the php.ini more or less. You should be using run-tests.php
switches -u, -U and -N.
Try: php run-tests.php -h
best regards
marcus
Tuesday, May 15, 2007, 1:33:28 PM, you wrote:
> Zoe Slattery wrote:
>> Antony Dovgal wrote:
>>> On 05/15/2007 12:44 PM, Zoe Slattery wrote:
On 05/15/2007 02:46 PM, Zoe Slattery wrote:
Antony Dovgal wrote:
On 05/15/2007 12:44 PM, Zoe Slattery wrote:
We're on it :-) Will probably have a few more questions on Unicode
testing later, noticed that you are putting UEXPECT section in tests-
but need to understand the implemenentation plan
Zoe Slattery wrote:
Antony Dovgal wrote:
On 05/15/2007 12:44 PM, Zoe Slattery wrote:
We're on it :-) Will probably have a few more questions on Unicode
testing later, noticed that you are putting UEXPECT section in
tests- but need to understand the implemenentation plan first...
We have two
Antony Dovgal wrote:
On 05/15/2007 12:44 PM, Zoe Slattery wrote:
We're on it :-) Will probably have a few more questions on Unicode
testing later, noticed that you are putting UEXPECT section in tests-
but need to understand the implemenentation plan first...
We have two operation modes in PH
On 05/15/2007 12:44 PM, Zoe Slattery wrote:
We're on it :-) Will probably have a few more questions on Unicode
testing later, noticed that you are putting UEXPECT section in tests-
but need to understand the implemenentation plan first...
We have two operation modes in PHP6 - "native" and Unic
Antony Dovgal wrote:
On 05/15/2007 11:52 AM, SoftVirus wrote:
Hello Zoe, Marcus & Tony,
Files names having _(basic|variation|error|object).phpt looks much
better.
File names _[0-9]*.phpt does not give much detail about what are the
functions being testing by this testcase until one looks at
On 05/15/2007 11:52 AM, SoftVirus wrote:
Hello Zoe, Marcus & Tony,
Files names having _(basic|variation|error|object).phpt looks much better.
File names _[0-9]*.phpt does not give much detail about what are the
functions being testing by this testcase until one looks at the --TEST--
section of
Hello Zoe, Marcus & Tony,
Files names having _(basic|variation|error|object).phpt looks much better.
File names _[0-9]*.phpt does not give much detail about what are the
functions being testing by this testcase until one looks at the --TEST--
section of the file. It would be nice to have the nam
Marcus Boerger wrote:
Hi Marcus & Tony
Hello Zoe,
that's pretty fine. Instead of _[bveo][0-9]?.phpt you could do
_(basic|variation|error|object)[0-9]{3}.phpt. Which is a tad bit better.
However those are just filenames helping you to find the correct test
file while developing. For that reaso
Hello Zoe,
that's pretty fine. Instead of _[bveo][0-9]?.phpt you could do
_(basic|variation|error|object)[0-9]{3}.phpt. Which is a tad bit better.
However those are just filenames helping you to find the correct test
file while developing. For that reason we didn not do so much about
generating
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 <[EMAIL PROTECTED]>
To: Zoe Slattery <[EMAIL PROTECTED]>
CC: Jani Taskinen <[
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 di
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
19 matches
Mail list logo
