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.
Our app has used data-test since long before we adopted SDODS. I set it in the project file:
testIdAttribute: data-testHeal report suggests getByTestId('cart-badge') for a locator that healed. I pasted that into the page object expecting it to look for data-testid and fail. It works. I would like to understand why before I trust it in twenty other places.
Accepted answer
getByTestId does not name an attribute — it looks up whichever attribute the runner was configured with. SDODS builds the Playwright projects from your resolved config and sets use.testIdAttribute from the project's testIdAttribute, so on your project getByTestId('cart-badge') resolves [data-test="cart-badge"], both in your page objects and in the healer's probes.
The suggestion is therefore correct and portable: change the attribute in one place and every test id locator follows.
Confirm which layer produced the value with:
sdods config show -p shop-web -e staging --explainOne thing to watch: testIdAttribute is a project-level key. We tried to override it per environment and it simply did not take. envs/<env>.yaml may override screenshots, heal, timeouts and perf, and that is the whole list.
If your environments genuinely disagree about the attribute, you have two projects rather than one.
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.