Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
We turned healing on for our checkout page object and the button still fails exactly the way it did before. No heal event, nothing in the log, just the Playwright timeout.
readonly checkout = this.heal.locator(this.page.locator('.btn-primary'), {
description: 'checkout button',
});The run output:
Error: locator.click: Timeout 15000ms exceeded.
Call log:
- waiting for locator('.btn-primary')heal.enabled is true and click is in heal.actions. What am I missing?
Accepted answer
Your context has nothing to build candidates from. description is a label for reports and history keys, not a strategy — the candidate list comes from role and name, testId, label, placeholder, title, altText, text and css. With only a description there are zero candidates, so the healer re-throws the original error rather than inventing one. That is why you see the plain timeout and no heal event.
Give it something to probe:
readonly checkout = this.heal.locator(this.page.locator('.btn-primary'), {
role: 'button', name: 'Checkout', testId: 'checkout', description: 'checkout button',
});.btn-primary is the weakest thing you could have picked as the primary. getByRole('button', { name: 'Checkout' }) as the primary and the CSS in the context is the right way round.Adding to that — the ordering in the docs is not decoration, it is the base score. role and name is 1.0, test id 0.95, label 0.9, placeholder 0.8, exact text 0.7, partial text 0.5, css 0.4. So a context that only carries CSS can never clear the default minScore of 0.6 even in the best case, and buys you nothing.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.