note that this patch:
1) is work in progress
2) contains nothing but tests.
3) only enables modules, disabling them and uninstalling them.
4) depends on at least #516150: Add fallback for main content block rendering getting in.
5) exposes some broken stuff in HEAD
6) managed to get PHP errors from common.inc
7) should be future-proof when done.

CommentFileSizeAuthor
testing_broken_drupal.patch7.1 KBalexanderpas
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sun’s picture

Proper description, please.

chx’s picture

We already have tests for enabling and disabling modules please check/amend them as necessary instead of writing a new one thanks.

Status: Needs review » Needs work

The last submitted patch failed testing.

alexanderpas’s picture

@chx
We never had tests that test what happens when all modules get enabled at the same time.
We also never had tests that disables all modules.

knowing this, and seeing the amount of breakage this patch revealed, this test is an good addition.

also, this test should be working perfectly (when finished) when a new core module get's added.

@sun
The tests provided by this patch tests what happens when all core modules get enabled at the same time, (our current tests only tests one or two modules at the same time), what happens when all core modules gets disabled at the same time (adhering to required-by (when properly coded.)) and what happens when all core modules providing uninstallation are uninstalled at the same time.

alexanderpas’s picture

Assigned: Unassigned » alexanderpas
sun.core’s picture

Priority: Critical » Normal

Tests don't qualify as critical.

longwave’s picture

Issue summary: View changes
Status: Needs work » Closed (outdated)

Testing has moved on a long way, closing this as outdated.