Problem/Motivation

(From #1212992: Prevent tests from deleting main installation's tables when parent::setUp() is not called.)

  • If a test method disables a module during the course of the test's execution, that module's database tables will not be cleaned during tearDown(), because it retrieves the list of tables using drupal_get_schema().

    One test which shows this behavior is the Field API -> Field info tests (FieldInfoTestCase).

Proposed resolution

  • TBD

Remaining tasks

  • TBD

User interface changes

  • None.

API changes

  • None.

Comments

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm commented
Title: Tables are not deleted when a module is disabled during text execution » Tables are not deleted when a module is disabled during test execution
sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented
Status: Active » Closed (duplicate)

I didn't know of this issue. But apparently, my follow-up patch in #1541958-18: Split setUp() into specific sub-methods fixes this issue. So sorry! ;)

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented
Title: Tables are not deleted when a module is disabled during test execution » Tests for: Tables are not deleted when a module is disabled during test execution
Status: Closed (duplicate) » Active
amateescu’s picture

amateescu CreditAttribution: amateescu for Pfizer, Inc. commented
Issue summary: View changes
Status: Active » Closed (duplicate)

I've added tests that all test tables are deleted in #1713332-40: The SQLite database driver fails to drop simpletest tables.

Dave Reid’s picture

Dave Reid
he/him
Primary language English
Location Nebraska USA
CreditAttribution: Dave Reid as a volunteer commented

Related: #2507157: drupal_get_schema() not reset after disabling a module