Properties of dynamic execution
Report of dynamic test functions execution
contracts/common.md#principled-implementation Strict mode rethrows the first error of a function after the execution record and the listener have seen it; no further file is dispatched once a task has failed, and the returned promise rejects with that first failure only after the in-flight tasks have settled, so no test runs after the caller observes the failure.
contracts/common.md#clear-and-simple-design A one-line binding of the shared pipeline with the strict flag.
Prepare dynamic executor in strict mode.
Strict mode stops dispatching further modules after a failure and rejects after active module tasks settle. validate records test failures and continues instead.
Processing cost: The shared executor discovers modules once, dispatches each queue index once and walks each admitted export; this entry only selects the failure policy.
Reuse: Discovery and module loading are shared by the tests of one run. New runs rediscover files; Node owns module caching, so editing an already imported module does not promise reload in the same process.
Resource ownership: One run owns the discovered module queue, visited directory set and report. At most the requested number of module tasks are active, all are awaited before success or strict rejection, and returned records transfer to the caller. Listener failure also settles workers; cancellation and unloading Node cached modules are not provided.