dbt Fusion may run a package test marked disabled

A disabled test that still runs can block a release or hide a configuration misunderstanding. A dbt issue reports that Fusion 2.0.8 ignores a targeted +enabled: false override for one package generic test under data_tests, while a package-wide override changes selection. The reporter supplies a minimal configuration and dbt ls output. The case needs version-specific verification before changing policy.

Inspect the resolved selection

Pin the package and dbt versions, then run dbt ls for the targeted generic test. Compare its unique ID, package namespace and resource path with the override in dbt_project.yml. The dbt project and enabled-configuration references define the intended settings; a visually plausible YAML key is not proof that the node resolved as expected.

Test the smallest workaround

Try a staging override scoped to the exact package and test path, and rerun dbt ls and the narrow test selection. A package-wide disable may suppress unrelated protections, so treat it as a diagnostic control rather than an automatic production fix. Record which tests disappear, not only whether the command exits successfully.

Protect the release gate

If the targeted override fails on the installed Fusion build, keep the known-working runtime or document an explicit temporary selection rule with an expiry. Attach resolved manifest details and command output to the upstream issue. Recheck when upgrading; configuration behavior can change without altering the project file.

Adovo’s view

A test policy is whatever the runner actually selects. Configuration that looks right but resolves differently is an operational risk. Inspect the selected graph before using an override to justify a production release.