Problem/Motivation
Split off from the parent to keep all the migration system changes in one issue and, hopefully, easier to review.
It looks like the block migration tests for d6_block and d7_block will require changes to the migration and that is probably best dealt with in a separate issue.
Steps to reproduce
Proposed resolution
Copy the migrate fixtures to the aggregator module so that the aggregator tests are independent of future changes to the fixtures.
Move migrate related tests to the aggregator module
Remaining tasks
Review
Make a separate issue for the block migrations and tests.
A followup could be made in aggregator to add testing of aggregator Id conflicts. This is not tested in core so is a new test. I did check this locally and it works as expected.
User interface changes
API changes
Data model changes
Release notes snippet
Issue fork drupal-3265424
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
quietone commentedgrep finds the following;
1,2,3 - Still think should be handled in a separate issue
4,5,6 - has an @todo for removing when the module is removed from core.
This is now ready for review.
Comment #4
catchOpened #3265483: Handle block migration for modules moved to contrib for blocks.
Comment #5
danflanagan8@quietone, I still see a mention of
aggregatorinDrupal\Tests\migrate_drupal\Kernel\StateFileExistsin the declaration of$stateFileRequiredDoes that need a @todo as well?
How did that escape your grep in #3? I'm not a grep-spert myself. Is it that the
StateFileExistscontains neithermigratnotTest.php?Comment #6
quietone commented@danflanagan8, well spotted.
I have added an other @todo. Also filed an issue to fix the test file name, #3266443: Rename StateFileExists to StateFileExistsTest.
Comment #7
quietone commentedThere is an error in the migration functional tests, a bit of cleanup missed when those tests were refactored, and will be fixed in #3266491: Add content in migrate UI functional tests only when needed. Once that is done the new aggregator functional tests need a change. I have made an issue for that and added @todo #3267040: Remove @todo in migration functional tests.
I think this covers everything now.
Comment #8
daffie commentedLooks good to me.
Just a couple of nitpicks.
Comment #9
quietone commentedComment #10
quietone commentedI answered all the unresolved issues, setting back to NR
Comment #11
daffie commentedAll the threads on the MR are answered.
For me it is RTBC.
Comment #14
catchGot this from phpstan (and also the d7 version), but fixed on commit.
I'm slightly concerned about the duplication of test coverage in 9.4.x, but having the contrib and core modules as much in sync as possible seems better than worrying about that too much.
Committed/pushed to 10.0.x and cherry-picked to 9.4.x, thanks!