s2b/vite-asset-collector

<?xml version="1.0"?>
<!--
    Boilerplate for a functional test suite setup.

    This file is loosely maintained within TYPO3 testing-framework, extensions
    are encouraged to not use it directly, but to copy it to an own place,
    for instance Build/FunctionalTests.xml.
    Note FunctionalTestsBootstrap.php should be copied along the way.

    Functional tests should extend \TYPO3\TestingFramework\Core\Tests\FunctionalTestCase,
    take a look at this class for further documentation on how to run the suite.

    TYPO3 CMS functional test suite also needs phpunit bootstrap code, the
    file is located next to this .xml as FunctionalTestsBootstrap.php
-->
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/10.1/phpunit.xsd"
    backupGlobals="true"
    beStrictAboutTestsThatDoNotTestAnything="false"
    bootstrap="FunctionalTestsBootstrap.php"
    cacheDirectory=".phpunit.cache"
    cacheResult="false"
    colors="true"
    displayDetailsOnTestsThatTriggerDeprecations="true"
    displayDetailsOnTestsThatTriggerErrors="true"
    displayDetailsOnTestsThatTriggerNotices="true"
    displayDetailsOnTestsThatTriggerWarnings="true"
    failOnDeprecation="true"
    failOnNotice="true"
    failOnRisky="true"
    failOnWarning="true"
    requireCoverageMetadata="false"
>
    <testsuites>
        <testsuite name="Functional tests">
            <!--
                This path either needs an adaption in extensions, or an extension's
                test location path needs to be given to phpunit.
            -->
            <directory>../../Tests/Functional/</directory>
        </testsuite>
    </testsuites>
    <php>
        <ini name="display_errors" value="1" />
        <env name="TYPO3_CONTEXT" value="Testing" />
        <env name="typo3DatabaseDriver" value="pdo_sqlite" />
    </php>
    <source>
        <include>
            <directory suffix=".php">../../Classes/</directory>
        </include>
    </source>
</phpunit>