File: getPHPUnitExtensionsAndSkins.php

package info (click to toggle)
mediawiki 1%3A1.43.3%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 417,464 kB
  • sloc: php: 1,062,949; javascript: 664,290; sql: 9,714; python: 5,458; xml: 3,489; sh: 1,131; makefile: 64
file content (46 lines) | stat: -rwxr-xr-x 2,109 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
#!/usr/bin/env php
<?php

/**
 * WARNING: Hic sunt dracones!
 *
 * This script is used in the PHPUnit bootstrap to get a list of extensions and skins to autoload,
 * without having the bootstrap file itself load any settings. It is a HUGE but unavoidable hack,
 * if we want to avoid loading settings in unit tests, and at the same time only load the extensions
 * enabled in LocalSettings.php without triggering any other side effects of Setup.php and the other
 * files it includes.
 * One day this may become unnecessary if we enforce YAML settings with a static list of extensions
 * and skins (https://www.mediawiki.org/wiki/Manual:YAML_settings_file_format).
 * The script was introduced for T227900, the idea being to have a single config file that can be used
 * with both unit and integration tests.
 * @internal This script should only be invoked by bootstrap.php, as part of the PHPUnit bootstrap process
 */

use MediaWiki\HookContainer\HookRunner;
use MediaWiki\MediaWikiServices;
use MediaWiki\Registration\ExtensionRegistry;

require_once __DIR__ . '/bootstrap.common.php';

TestSetup::loadSettingsFiles();

$extensionsAndSkins = ExtensionRegistry::getInstance()->getQueue();

echo implode( "\n", array_keys( $extensionsAndSkins ) );

echo "\n\nTESTPATHS\n\n";

// Build a list of extension tests, based on autodiscovered tests as well as tests added with the
// UnitTestsList hook. The list is only to be used in ExtensionsTestSuite.
// This is a hack inside the hack, motivated by the fact that we can't access MediaWikiServices, or even
// just the config needed to create a hook container, as early as when ExtensionsTestSuite::suite is called.
// This particular hack can be removed once the UnitTestsList hook is removed (T298509)
$registry = ExtensionRegistry::getInstance();
$paths = [];
foreach ( $registry->getAllThings() as $info ) {
	$paths[] = dirname( $info['path'] ) . '/tests/phpunit';
}
// Extensions can return a list of files or directories
( new HookRunner( MediaWikiServices::getInstance()->getHookContainer() ) )->onUnitTestsList( $paths );

echo implode( "\n", $paths );