Tests repository (run-tests.php) View as Markdown

On Fri, Mar 12, 2010 at 11:18, Jani Taskinenjani.taskinen@iki.fi
wrote:

Having tests in multiple branches is PITA. Hasn't anyone considered that
the
best way would be to move all tests into their own repository
(directory..whatever :) in SVN..? Considering they are supposed to be
used
for testing against regressions and BC breaks, they should always be
runnable using any PHP version?

Thats actually a fairly good idea.

Some tests however are not supposed to work in earlier releases, so we
need to either add a new
==SKIP-VERSION==
5.2, 5.1, 5.0

Perhaps something like required min version is better.

Any ideas who has been working on the improved test stuff? Or was that just
a dream?

First of all, I apologize for the subject line change, but this really is a
different issue than the test repository itself.

It was started by George during last years GSOC. Zoe and Stefan were also
working on it after GSOC ended. Both Zoe and Stefan ran out of time and it
went dormant for a bit. I contacted Zoe about the status and offered to pick
it up, but I also offered to organize TestFest this year.

--Jani

--

I really do want to do both but I can't do both at the same time as they
both will be big time sinks for a part time volunteer.

Solutions:

1. I continue to work on TestFest and then work on run-tests.php as soon as
   the TestFest load lightens up enough to allow it.

2. Someone else picks up run-tests.php and I focus solely on TestFest.

3. Someone else picks up TestFest and I focus solely on run-tests.php.

My vote is option 1 as I really like both projects. But it wouldn't be fair
for me to slow either down if the need for both is pressing.

Eric Lee Stewart