Re: 4.0.2 Release date
| From: | Stig Sæther Bakken | Date: | Fri, 04 Aug 2000 12:48:20 +0000 |
| Subject: | Re: 4.0.2 Release date | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-27681@lists.php.net to get a copy of this message | ||
Zak Greant wrote:
>
> Hello All,
>
> I have asked the QA team to get ready for the upcoming release. Everyone
> who has so far committed to testing the release candidate is listed at
> http://qa.php.net/release.4.0.2.php
>
> If the developers have any special requests, they should make them now. :)
>
> Also, if anyone else would like to list themselves so that we have a better
> idea of what platforms are available for testing, that would be great.
>
> I am going to be developing rough test scripts that I will redistribute as
> they are ready. The scripts will be quite simple and will follow the php
> manual's structure.
Zak,
PHP has been in need of a fully automated regression testing system
again for a while. We used to have one, but most people find tests
almost as boring to write as documentation, so it was dissolved by the
time we released 3.0.
I've started experimenting with a framework for this in the pear subdir
(see pear/run-tests.in). It's modular by defining a subdir in every dir
called "tests" where test scripts (written in PHP) and their expected
output are stored in files called "testname.t" and "testname.o" (plus
maybe a "testname.i" file if the test needs file input).
What if the QA team members, whenever using test scripts to verify that
a bug is really gone, put their test code into this or a similar
structure, so we can "re-use" your efforts automatically? That way we
at least get regression tests for all bugs that are fixed.
I assume I'm not the only one who finds pleasure in seeing screenfull
upon screenfull of "test passed" ;-).
- Stig