Sometimes we have patches that add an update function. If these update functions have errors or undefined functions they currently are not caught by the test bot since it installs an instance *after* applying the patch. Is there a way we could have these added update functions tested? Thinking out loud... maybe have one of the test bots try and install a clean version of Drupal first, apply patch next, run any new update functions and then perform tests.

Comments

boombatower’s picture

boombatower commented
Status: Active » Postponed (maintainer needs more info)

Really not sure that makes a lot of sense. I mean would just detect an update hook and then run clean -> patched? Plus we can't test the update hooks together.

I would recommend implementing #377856: Provide D6 to D7 update test which should allow you to test all update hooks.

boombatower’s picture

boombatower commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

Seems like other issue is what we want, and I'll be finishing it once the browser gets in.