Hi,
Just a few words about tests :
I made an interface to aggregate all failed results on all PHP versions.
This was for internal purposes in my company, but I would be glad if it can
help to catch all failing tests (most are failing because of the test
itself).
If you think such a tool can be helpful and want to see additional features,
feel free to ask. If not .. Well sorry for the noise ;)
Also, Rasmus, you talked about time need to make all tests. More than a year
ago, there was a project undergoing with parallel execution of all tests. I
asked about it a few months ago and did not get any feedback. Is this
project dead ? I'm willing to take it back on tracks ;) I would need some
help to know where / why the project was stopped.
Olivier
Hi,
Just a few words about tests :
I made an interface to aggregate all failed results on all PHP versions.
This was for internal purposes in my company, but I would be glad if it can
help to catch all failing tests (most are failing because of the test
itself).If you think such a tool can be helpful and want to see additional
features,
feel free to ask. If not .. Well sorry for the noise ;)Also, Rasmus, you talked about time need to make all tests. More than a
year
ago, there was a project undergoing with parallel execution of all tests. I
asked about it a few months ago and did not get any feedback. Is this
project dead ? I'm willing to take it back on tracks ;) I would need some
help to know where / why the project was stopped.Olivier
nice, good to hear that.
I'm absolutly positive that speeding up the test execution would be more
likely that the testsuite has been ran before commiting changes...
Tyrael
Hi,
Just a few words about tests :
I made an interface to aggregate all failed results on all PHP versions.
This was for internal purposes in my company, but I would be glad if it can
help to catch all failing tests (most are failing because of the test
itself).If you think such a tool can be helpful and want to see additional features,
feel free to ask. If not .. Well sorry for the noise ;)
I think it would be great to have this on qa.php.net
Can you post the src for review (to php-webmaster@lists.php.net as
there is where we discuss all web stuffz) before committing it?
-Hannes
Hi,
I think it would be great to have this on qa.php.net
Can you post the src for review (to php-webmaster@lists.php.net as
there is where we discuss all web stuffz) before committing it?
I'm glad to see some positive feedback :) Let me slightly cleanup the code
and I'll post src asap.
By the way, I fixed the bug visible on
http://news.php.net/php.internals/52242
But I do not have write access to this folder (svn account odoucet).
Please find patch attached.
Olivier
Hi,
I think it would be great to have this on qa.php.net
Can you post the src for review (to php-webmaster@lists.php.net as
there is where we discuss all web stuffz) before committing it?I'm glad to see some positive feedback :) Let me slightly cleanup the code
and I'll post src asap.
By the way, I fixed the bug visible
on http://news.php.net/php.internals/52242
But I do not have write access to this folder (svn account odoucet).
You do now.
Please find patch attached.
Please fix the whitespace issue before committing.
And please post these sort of things to php-webmaster@ :)
-Hannes
Hi!
I made an interface to aggregate all failed results on all PHP versions.
This was for internal purposes in my company, but I would be glad if it can
help to catch all failing tests (most are failing because of the test
itself).
I've started a page for this: https://wiki.php.net/todo/tests54
but yours looks way better. So here go the feature requests:
-
It'd be great to be able to contribute a report manually (say, the
bug only happens on specific OS/configuration, which is not run by QA
machines). So ability to get a saved report file in there would be helpful. -
It'd be nice to get this also running for trunk (and/or soon 5.4
branch).
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227