Re: Implement formal process for run-tests.php refactor
| From: | Johannes Schlüter | Date: | Thu, 18 May 2017 00:35:58 +0000 |
| Subject: | Re: Implement formal process for run-tests.php refactor | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-99089@lists.php.net to get a copy of this message | ||
On Mi, 2017-05-17 at 23:30 +0200, Marco Pivetta wrote:
> Is Sebastian copied in here? Why can't we just use the super-battle-
> tested
> PHPUnit? It supports phpt and a ton of plugins, plus everyone uses it
> and
> is familiar with it.
PHPUnit is huge. run-tests is a small script in a single file which I
can quickly edit. For PHPUnit I have multiple files and need tooling to
phar them up.
PHPUnit (according to it's website) also has more dependencies (DOM and
JSON) which are not included in --disable-all. used
I'm not sure if PHPUnit meanwhile supports redirect tests as in PDO.
Is there a performance comparison? - make test runs for a loooong time.
A difference might have an impact. (both ways round ;) )
To the original question: Granting run-tests.php karma is trivial. We
can easily give access to people working on it. While contributors
should be aware that this is a key component f the PHP development :-)
johannes