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.
sdods heal report --lastI get a table with description, original, occurrences, succeeded, strategy and suggested. Most of it I can guess. Two I cannot:
occurrences is 12 but succeeded is 9 — where did the other three go, and why is the row still in a report about heals?strategy reads role×7 testid×2. Why two different ones for the same locator?Accepted answer
Rows are keyed on description plus original selector, and every event is counted whether or not it found anything. So occurrences: 12, succeeded: 9 means that locator's primary failed twelve times, and on three of those no candidate cleared minScore — those three are the runs where your scenario died with HEAL_FAILED. The row stays because the failures are the interesting half.
strategy counts only the successful ones, by winning strategy. role×7 testid×2 means the role and name candidate won seven times and the test id twice. That usually means the accessible name is not stable: the element is there both times, but on two runs the name did not match and the test id picked up the slack. Worth a look, because whatever is moving the name will eventually move it past recognition.
suggested is the last selector that actually won, which is what you would paste into the page object.
Add --all when you want the same table across every run under the artifacts directory rather than just the last one. That is where the pattern shows up. A locator that heals once is a bad day; one that heals in nine runs out of ten is a page object nobody has updated.
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.