Change Details

Integration Tests is too slow to development: TDD or refactoring, Docker env, prepare DB for each run It makes development slow. Some integration tests not dependent on database preparation and but more than a unit tests. It's the usual situation for SOLID / GRASP development or refactoring. We needed in ServiceContainer, global configs, legacy support We can separate integration tests into light and full. use traits or class extensions to DRY proof of concept: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/568491/1/tests/phpunit/includes/content/ObjectFactoryMakeContentHandlerWithSpecsToTest.php ------------------ We can also prepare MediaWikiService for easy use in unit tests. Change return of method: MediaWikiService::foceGlobalInstance to void

===Motivation Integration Tests are too slow for development: TDD or refactoring, Docker env, prepare DB for each run It makes development slow. Some integration tests don't depend on a database in fact and can be run as pure unit tests. It's the usual situation for SOLID / GRASP development or refactoring. We needed in ServiceContainer, global configs, legacy support We can split integration tests into a light (pure unit tests) and full. Traits or class extensions can be used to DRY. proof of concept: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/568491/1/tests/phpunit/includes/content/ObjectFactoryMakeContentHandlerWithSpecsToTest.php ------------------ We can also prepare MediaWikiService for easy use in unit tests. Change return of method: MediaWikiService::foceGlobalInstance to void

===Motivation Integration Tests isare too slow tofor development: TDD or refactoring, Docker env, prepare DB for each run It makes development slow. Some integration tests nodon't dependent on on a database preparation and but more than ain fact and can be run as pure unit tests. It's the usual situation for SOLID / GRASP development or refactoring. We needed in ServiceContainer, global configs, legacy support We can separateplit integration tests into a lightt (pure unit tests) and full. use t Traits or class extensionsns can be used to DRY. proof of concept: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/568491/1/tests/phpunit/includes/content/ObjectFactoryMakeContentHandlerWithSpecsToTest.php ------------------ We can also prepare MediaWikiService for easy use in unit tests. Change return of method: MediaWikiService::foceGlobalInstance to void