[TASK] Functional tests without phpunit process isolation 29/57129/19
authorChristian Kuhn <lolli@schwarzbu.ch>
Tue, 5 Jun 2018 23:12:07 +0000 (01:12 +0200)
committerWouter Wolters <typo3@wouterwolters.nl>
Wed, 25 Jul 2018 20:44:10 +0000 (22:44 +0200)
commit81244e10cb0959ede7d570fc89f46a64901ba744
tree24d1ceab384b8e42521d51c02782abd4e39175bc
parentab0666b2c42ae7259a3bbf9eafc9e7068380386e
[TASK] Functional tests without phpunit process isolation

We're finally able to manage our core internal framework state,
at least in the backend. This is a huge step. To proof this,
functional tests now execute without process isolation.

We need a couple of additional reset state methods. Those are
for now marked @internal to allow us changing this stuff if
needed later.

The SystemEnvironmentBuilder also needs a change to not
directly rely on PATH_thisScript anymore.

composer require --dev typo3/testing-framework ~4.1.0

Change-Id: I37fbee7e4cf6ccb2eec18d057b6b9671d6a85167
Resolves: #85649
Releases: master
Reviewed-on: https://review.typo3.org/57129
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Reviewed-by: Wouter Wolters <typo3@wouterwolters.nl>
Tested-by: Wouter Wolters <typo3@wouterwolters.nl>
composer.json
composer.lock
typo3/sysext/core/Classes/Core/SystemEnvironmentBuilder.php
typo3/sysext/core/Classes/Database/ConnectionPool.php
typo3/sysext/core/Classes/Utility/GeneralUtility.php
typo3/sysext/core/Tests/Functional/Cache/Backend/MemcachedBackendTest.php
typo3/sysext/core/Tests/Functional/Cache/Backend/RedisBackendTest.php
typo3/sysext/core/composer.json