Block plugin derivatives (and maybe all derivatives?) that make calls to the database or calls to module specific functions from the module that they are owned by, create errors when running simpletest.

I ran into the when working on #1535868: Convert all blocks into plugins

I talked to timplunkett and neclimdul about it on IRC and we agreed that for now, we will just put a module_exists in the derivates so we can move forward and stop tests from failing miserably. I am putting a todo in the derivatives with a link to this issue.

This should be fixed somewhere else at some point. Maybe in the testing framework itself.

Comments

naxoc’s picture

naxoc CreditAttribution: naxoc commented
Title: Plugin derivatives calling un-enabled modules in tests » Plugin derivatives calling disabled modules in tests

Better title. Don't think un-enabled is a word :)

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
CreditAttribution: tim.plunkett commented

I think this might be a duplicate (or at least a symptom) of #1780396: Namespaces of disabled modules are registered during test runs

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy commented

We have seen the same problem when working with edit module plugins.

podarok’s picture

podarok
🇺🇦 he/him/his
Primary language Ukrainian
Location Ukraine
CreditAttribution: podarok commented

#3 related #1935132: Invalid argument supplied for foreach() in Drupal\Core\Plugin\Discovery\AnnotatedClassDiscovery->__construct()

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers commented
Status: Active » Closed (duplicate)

This is indeed a dupe of #1780396: Namespaces of disabled modules are registered during test runs AFAICT. Apologies if that's not true.