facebook/hhvm — pull request #3574 by tmotyl (2014-08-24 15:14:19+00:00)
Title: Add TYPO3 Unit tests to the OSS framework parity check

Third try to include TYPO3 tests in HHVM parity check :)
fixes: https://github.com/facebook/hhvm/issues/2103

This patch was tested on Centos 6.4 with HHVM compiled from sources 730e11dc2f69a3d40270dbd60f547428df0a480d

The problem was that TYPO3 unit tests were working on Ubuntu, but not on Centos.
I've spend some time debugging on Centos and found out that the whole
test suit runs properly (without fatals). The master process receives the
```Tests: 6701, Assertions: 8610, Failures: 69, Errors: 33, Skipped: 146.```
but for some reason doesn't recognize it.

This patch contains a workaround so all TYPO3 unit test suite runs, and returns valid stats:
```
[vagrant@vagrant-centos64 hphp]$ hhvm test/frameworks/run.php --csv --csvheader typo3
date, typo3
2014/08/24-14:06:53,98.42
```
However there is probably still sth wrong with the test runner.

A little explanation of the workaround:

A custom phpunit xml configuration file is created,
because for some reason test runner returned "SUMMARY: typo3=FATAL"
with default TYPO3 phpunit configuration, which contained sth like this:
```

../../../../typo3/sysext/*/Tests/Unit/

```
I've tried to run unit tests of all core extensions one after another (separate entries in the xml) and managed to narrow down the issue to the extension "Form"

So I've broken down the configuration for each extension folder
instead of using wildcard.
However HHVM still couldnt return the stats, when running just test for "Form" extension alone
```
../../../../typo3/sysext/form/Tests/Unit/
```

However if you list all Form unit tests separately, it works.
So as a workaround all Form tests are listed in the phpunit xml
configuration file.