Problem/Motivation

Many of migrate_drupal's PHPUnit tests are not true unit tests, but integration tests, because they rely on a database. Once the fake DB driver is gone (in #2499835: Remove broken Fake DB driver), they will be relying on SQLite, but still (ultimately) extending UnitTestBase.

Proposed Resolution

The tests should be converted to kernel tests, based on #2304461: KernelTestBaseTNG™. That way they can keep all their PHPUnit-ey goodness, but use a real database. Because that's what integration tests do. Until KTBNG lands, this is postponed.

Remaining Tasks

  • Make any PHPUnit-based migrate_drupal test which relies on a database into a kernel test
  • Review the patch
  • Commit it
  • Rejoice

Comments

phenaproxima’s picture

Status: Postponed » Active

Unblocked!

mikeryan’s picture

Referring to the change notice:

Until Drupal 8.0.x just straight conversions are allowed to land in core itself. What are straight conversions. Straight conversions are conversions that just change the base class

(see the change notice for details on acceptable changes, e.g. file moves).

Now, I wonder if Migrate can be a little more flexible, since we're still kind of pre-beta?

neclimdul’s picture

Status: Active » Postponed
phenaproxima’s picture

Version: 8.0.x-dev » 8.1.x-dev

No longer blocked, but still postponed until Drupal 8.0 is tagged. I think this is a good 8.1 target.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

mikeryan’s picture

Status: Postponed » Active

This can be done any time now...

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.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.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.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.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.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.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.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.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.

heddn’s picture

Status: Active » Closed (won't fix)

I don't think this is going to get changed at this late time in the game.