Change Details

Currently, core tests cannot be run by running the `phpunit` command directly. Instead, we have a custom entrypoint that wraps PHPUnit and calls it programmatically from `tests/phpunit/phpunit.php`. We can convert all our logic in the wrapper to a PHPUnit bootstrap file (done already in tests/phpunit/bootstrap.php), so that we (and other automated tools) can start PHPUnit through the regular entry point. Next steps: [] Remove suite.xml {T227900} [x] Move everything from phpunit.php to the bootstrap file [] Delete phpunit.php and fix everything that refers directly to it [] Fix deprecation warnings with dataProviders accessing MW services {T297292}

Currently, core tests cannot be run by running the `phpunit` command directly. Instead, we have a custom entrypoint that wraps PHPUnit and calls it programmatically from `tests/phpunit/phpunit.php`. We can convert all our logic in the wrapper to a PHPUnit bootstrap file (done already in tests/phpunit/bootstrap.php), so that we (and other automated tools) can start PHPUnit through the regular entry point. Next steps: [x] Remove suite.xml {T227900} [x] Move everything from phpunit.php to the bootstrap file [x] Delete phpunit.php and fix everything that refers directly to it [x] (no longer needed) Fix deprecation warnings with dataProviders accessing MW services {T297292}

Currently, core tests cannot be run by running the `phpunit` command directly. Instead, we have a custom entrypoint that wraps PHPUnit and calls it programmatically from `tests/phpunit/phpunit.php`. We can convert all our logic in the wrapper to a PHPUnit bootstrap file (done already in tests/phpunit/bootstrap.php), so that we (and other automated tools) can start PHPUnit through the regular entry point. Next steps: [x] Remove suite.xml {T227900} [x] Move everything from phpunit.php to the bootstrap file [x] Delete phpunit.php and fix everything that refers directly to it []x] (no longer needed) Fix deprecation warnings with dataProviders accessing MW services {T297292}