We have one scenario whose entire job is to assert that the design system has not moved the primary action button. Healing makes it unfalsifiable — it heals to the role and passes no matter what we do to the markup.
Everything I can find is project or environment scoped. Is there a per-scenario or per-tag switch?
Accepted answer
No per-scenario switch. Heal configuration resolves through the config layers and lands on the project, so the smallest unit you can disable it for is an environment.
For your case you do not want the switch anyway, you want the locator. Use .raw and assert on the primary directly:
async assertPrimaryActionUnchanged() {
await expect(this.submit.raw).toBeVisible();
}raw hands you the underlying Playwright locator with no healer in front of it, so the assertion fails the moment the primary stops matching. Two lines, scoped exactly to the thing you care about.
Same conclusion from a different direction. A scenario asserting "the markup has not changed" is really a contract test, and contract tests should not share a mechanism with the scenarios that are supposed to be resilient. We keep ours in a separate feature and reach for raw throughout it — no config, and no surprises when somebody edits sdods.project.yaml.
If you ever do want it environment-wide, heal: { enabled: false } in envs/<env>.yaml works, since the env layer may override heal.
Have a different question? Ask it.