Re: The new run-tests.php...
| From: | Georg Gradwohl | Date: | Fri, 03 Jul 2009 12:31:10 +0000 |
| Subject: | Re: The new run-tests.php... | ||
| References: | 1 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-65178@lists.php.net to get a copy of this message | ||
Am 02.07.09 18:51 schrieb "Stefan Priebsch" unter
<stefan.priebsch@e-novative.de>:
> zoe schrieb:
>>> I did not like that it does not flush status reports. Scripts that
>>> output nothing are hard to monitor and look "dead". In particular in
>>> automated setups it may become tricky to find out if the script is
>>> dead or still runs. Is there already an option to enable constant
>>> output? No, a status bar with a percentage counter would not make me
>>> happy.
>> You will get it. We don't like the way it is right now either. We have
>> it like this at the moment because we are running directories in
>> parallel and collecting up the output at the end of each task is easier.
>> But we know we have to implement a status reporter. No guarantees on
>> when :-)
>> I will add it to the to-do list
>>
>> Stefan, Georg - please add comments :-)
>
> I'm nodding.
>
> Currently our main focus is to integrate concurrent test execution
> properly into run-tests, which is what Georg is working on. We want to
> do it in a way so we can also support concurrent test execution on
> Windows in a next step, that's why we want to make sure it's not just
> working, but is done right.
>
> Stefan
I completely agree. My next task is to rebuild the outputWriter. After that
it will be easy to add a live-output. I would suggest that by default a dot
per test-group is printed (like phpunit) and we are providing an option to
print out a detailed report. What do you think?
g2