Problem/Motivation

#2661542-10: Isolate Drupal\Tests\Component\Plugin\DefaultFactoryTest from core test module brings up a good point. We have a lot of different versions of how to specify a fixtures directory.

$ cd core/
$ find . -iname 'fixture*' -type d
./modules/block/tests/fixtures
./modules/content_moderation/tests/fixtures
./modules/dblog/tests/fixtures
./modules/field/tests/fixtures
./modules/file/tests/fixtures
./modules/hal/tests/fixtures
./modules/media/tests/fixtures
./modules/migrate_drupal/tests/fixtures
./modules/rest/tests/fixtures
./modules/simpletest/tests/fixtures
./modules/system/tests/fixtures
./modules/user/tests/fixtures
./modules/views/tests/fixtures
./tests/Drupal/Tests/Component/Annotation/Fixtures
./tests/Drupal/Tests/Component/DependencyInjection/Fixture
./tests/Drupal/Tests/Component/Diff/Engine/fixtures
./tests/Drupal/Tests/Component/FileCache/Fixtures
./tests/Drupal/Tests/Component/Utility/fixtures
./tests/Drupal/Tests/Core/Config/Entity/Fixtures
./tests/Drupal/Tests/Core/DependencyInjection/Fixture
./tests/Drupal/Tests/Core/DrupalKernel/fixtures
./tests/Drupal/Tests/Core/Form/fixtures
./tests/Drupal/Tests/Core/Plugin/Discovery/Fixtures
./tests/Drupal/Tests/Core/Plugin/Fixtures
./tests/fixtures

So we have some plural, some uppercase.

In modules we seem to have normalized on fixtures/ (lower case, plural).

Other places not so much.

Proposed resolution

Follow the lead of module tests and use lower-case plural.

Rename test fixture directories in core this way.

Fix tests that need them.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

Mile23 created an issue. See original summary.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

joachim’s picture

joachim commented

Furthermore, there are fixtures in multiple places for the same group of tests!

e.g.:

- core/tests/fixtures/plugins
- core/tests/Drupal/Tests/Component/Plugin/Fixtures

and that also probably has fixtures for Core-core, so we have this pair too:

- core/tests/fixtures/plugins
- core/tests/Drupal/Tests/Core/Plugin/Fixtures

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.