typo3/testing-framework provides some template files as kickstart
for project and extension based testing. They are properly marked
to be copied and not used directly from the package. The reason
for this recommendation is, that project should make adjustments
to theire concrete setup, like coverage settings and so on.
This change clonses the corresponding template files from the
testing-framework to folders in this extension, adjusts needed
paths and ensure testing is still working. With that this best
practice example follows the recommendation and best-practice
for typo3/testing-framework usage.
Tasks
* provided cloned unit- and function test configuration and
bootstrap files in `Build/phpunit/`
* updated cloned phpunit configuration files to be phpunit v9
compatible, removing old coverage tag as this is done by
cli options in this repository anyway
* add proper xml namespacing to cloned phpunit configurations
* adjustes config paths in unit and functional testing calls
provided as composer scripts
* adjusted phpunit configuration files in documentation
Resolves#533
