Re: QA Reports aggregator
| From: | Philip Olson | Date: | Fri, 13 May 2011 22:22:12 +0000 |
| Subject: | Re: QA Reports aggregator | ||
| References: | 1 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-10999@lists.php.net to get a copy of this message | ||
On May 13, 2011, at 10:16 AM, Olivier Doucet wrote:
> Hello everyone,
>
> I created a tool that parse QA Reports email and aggregate them on a nice
> interface.
> It is then easy to see which tests are most failing. It appears most of the
> time this is the test itself that is not working.
>
> The interface can be seen live on http://phpqa.ajeux.net/
Greetings Olivier,
This is great and going to help the QA process.
A few random ideas:
A configuration for prominent versions. Currently 5.2.17 and 5.3.6 are featured, but 5.3.7-dev and
5.3.99-dev are what the QA team are most interested in. I was hacking the qa version include
(release-qa.php) last night, and now see that making the qa versions available would be useful so we
could try that. A simple serialized array should work, and then saved as something like
'cache/qa-releases.txt'.
And each 'Version' should link to its own page/tab with failed test information.
As for getting the tests, how do we deal with the IMAP setup? I also wonder if we should start
saving test results on the server instead of only to the php.qa.reports list, and then parse those.
Probably KISS and not worry about it but it's worth thinking about as a potential TODO item
down the road.
> - uniform spacing. I personnaly would like to follow this guideline :
>
> http://framework.zend.com/manual/en/coding-standard.coding-style.html
> If there is already a specific guideline for php tools, please let me know.
> I already have to make sure I followed this standard throughout all files ;)
Coding standards used within php.net code is "whatever you want" but in theory we use the
PEAR CS.
Regards,
Philip