test: make parallel/test-bootstrap-modules easier to reason about

[refack]

• Version: N/A
• Platform: All
• Subsystem: test,bootstrap

node/test/parallel/test-bootstrap-modules.js

Lines 1 to 14 in 5468509

	/* eslint-disable node-core/required-modules */
	'use strict';
	// Ordinarily test files must require('common') but that action causes
	// the global console to be compiled, defeating the purpose of this test.
	// This makes sure no additional files are added without carefully considering
	// lazy loading. Please adjust the value if necessary.
	const list = process.moduleLoadList.slice();
	const assert = require('assert');
	assert(list.length <= 78, list);

The test uses a magic number that can only be reasonably found empeericaly. That number also changes depending on what CLI parameters are used, or if run with a test harness.
Some suggestions for improvement have been:

1. blacklist some modules that we know we don’t want to have loaded unconditionally, rather than set a fixed number. (@addaleax)
2. Just reports from the CI or add something informative to the test runner output. (@devsnek)
3. ???

Refs: #23876

[devsnek]

fwiw my suggestion is now a whitelist of modules

[ho-dor]

Can I work on this as this has a good first issue tag? @refack

[Trott]

I kind of wonder if the test should be removed.