Re: 4.3.0-pre1 - Mac OS X results
| From: | Mark J. Hershenson | Date: | Fri, 11 Oct 2002 16:52:18 +0000 |
| Subject: | Re: 4.3.0-pre1 - Mac OS X results | ||
| References: | 1 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-6107@lists.php.net to get a copy of this message | ||
>> Before I got spammed...
>>
>> Apologies for the StuffIt compression on the attachments. I got a message
>> back from PAIR saying my mail had to be less than 40k, and base64'ing those
>> attachments made it 41k without an email body. :|
>
> It would help us if you didn't have to do this, can you please split it
> up into more mails instead? I'm afraid most people who work on PHP can
> not handle .sit files.
>
> Derick
Just a thought, but wouldn't it be a boon if the front-end system accepted
these types of files as well using file uploading?
As it was, creating multiple emails wasn't impossible nor overly involved,
but it still seems unintuitive, especially when the instructions only read:
"Please send the .log file accompanying that test case to
php-qa@lists.php.net if a test fails."
Additionally, the test system uses the same test case names in multiple
tests, meaning that there can be more than one "002.log" files, which mean
there seems an inherent limitation in what logs you can easily make publicly
available by, say, one's own webserver instead of multiple emails. I renamed
those files to avoid that issue, but perhaps it would be helpful if the
testing cases adopted a convention of:
{extension}-{testname}.{phpt|log}
Also, shouldn't the test program create a folder /tests/failures/ and
copy/move the .log files there so that there is one place to find failure
log files?
And one step further, shouldn't the test application prompt the user:
* Would you like to provide the error logs to the PHP QA team?
If yes, ask for their name and basic info about their system, and
then use PEAR to send those logs as email attachments to
php-qa@lists.php.net.
If not, exit, and let the user know that if they choose to do so in
the future, they can email their logs to the list.
It just seems to me that these little things could help the QA process
immensely to make reporting even more transparent to the user, and increase
the volume of submitted log files for analysis.
Mark J. Hershenson
markhers@green-ant.com
http://www.green-ant.com/