This information is from the code coverage report (see http://coverage.cwgordon.com/coverage).

We need to test:

1) menu_iterate().
2) module_list() with a fixed list.
3) Parsing an empty .info file.
4) Implementing hook_boot().
5) Circular dependency handling.
6) Nested dependency handling.
7) Node access rebuild properly triggered.
8) module_hook() when in MAINTENANCE_MODE.
9) module_invoke_all() with non-array returns.

Comments

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented
Status: Active » Postponed

Marking postponed until http://drupal.org/node/259412 is resolved. There's probably some bits that don't get affected by that patch, but if anyone's looking to start with testing, they shouldn't start with something that's in the process of getting reworked.

lilou’s picture

lilou CreditAttribution: lilou commented

See also #310617: Tests for module.inc

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
CreditAttribution: clemens.tolboom commented

See also #310898: Making module_enable and module_disable API functions which provides tooling for circular dependency and nested dependencies based on the whole dependency graph and Topological Sorted Lists.

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented
Status: Postponed » Active

Un-postponing this because the revamp patch is stalled.

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented
Component: tests » base system
Category: bug » task
Priority: Critical » Normal

Fixing the critical / pending bugs queues to reflect things which are really bugs or release critical.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented

I started looking at doing a patch for #222074: PHP bug/feature in array_merge_recursive() causes warning messages until this issue raised its head..

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented
Status: Active » Closed (won't fix)

This is so old, no one has run code coverage for more than a year, let's just close it.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented

Am confused. Does that mean code coverage isn't as important as previously mentioned, or that it's just so far down the priority list that nobody has had time to work on it? If it's the latter, wouldn't it be better to leave it Active or maybe Postponed?