Right now, updating or maintaining the migration database fixtures is very, very painful and time-consuming task. After a dev exported an updated database fixture, it's very hard to distinguish which changes we want to commit, and which ones we should revert (manually).
Based on the system module's schema, right now the core D7 DB fixture contains a Drupal 7.44 database. Refresh it to the most recent one (7.80), execute database updates, and then export the updated database with
php core/scripts/db-tools.php dump --database fixture_connection > core/modules/migrate_drupal/tests/fixtures/drupal7.php
(See Generating database fixtures for migration tests → ).
Add a new option for the DbDumpCommand which then generates a set of per-table fixture files.
Nothing
New option for DbDumpCommand.
Nothing.
TBD.
Needs work
10.1 ✨
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Should I open a separate issue for the problem of certain data structures being stored as serialized arrays with embedded objects ("config" and "key_value" values especially), which makes fixture files extremely complex?