In UpgradePathTestBase::performUpgrade(), there is the following comment:

// @todo Remove the try/catch when UpgradePathTestBase::setup() is fixed to
//   boot DrupalKernel (as WebTestBase::setup() does).

#1786990: [Module]Bundle is registered too late in WebTestBase::setUp() added TestBase::rebuildContainer(), which I think it needed here.

I think the comment is technically wrong, since the relevant parts of WebTestBase::setUp() are left to UpgradePathTestBase::performUpgrade().

This blocks any issue trying to use bundles during upgrade tests, hence it being major.

CommentFileSizeAuthor
#1 drupal-1816726-1.patch1.04 KBtim.plunkett
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tim.plunkett’s picture

Status: Active » Needs review
FileSize
1.04 KB

WebTestBase::setUp() sets up and completely installs Drupal.
UpgradePathTestBase::setUp() just gets the environment ready, and leaves the installing to UpgradePathTestBase::performUpgrade(), which is why the fix is in there.

tim.plunkett’s picture

Issue tags: +VDC

Tagging, since we need this for Views

tim.plunkett’s picture

The removed calls to drupal_flush_all_caches(), WebTestBase::refreshVariables(), WebTestBase::checkPermissions() are all contained in WebTestBase::resetAll()

effulgentsia’s picture

Status: Needs review » Reviewed & tested by the community

Looks fine to me and it's green. Nice to see that rebuilding the container makes the try/catch unnecessary.

webchick’s picture

Status: Reviewed & tested by the community » Fixed

I think I somehow committed this with something else. Woohoo?

Automatically closed -- issue fixed for 2 weeks with no activity.