Assert Text on Page (Custom UI) working not properly.

[OMT]

Hi, does anyone know why Assert Text on Page (Custom UI) sometimes fails to work properly and reports that some text is visible even it should not be on the page? I'm checking that some text is not on the page with the Assert Text on Page (not on the page) step, but it fails because it says that text is visible. I'm doing debugging and watching carefully, and verifying that the text is not on the page, but ATF says differently! 

[Ankur Bawiskar]

@OMT 

Custom UI steps are not always guaranteed to work and are not that much reliable.

There are some limitations with ATF when it comes to Custom UI steps

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[OMT]

I think it's not just looking at the text page, but at the DOM. I'm also not able to create a custom step to check only the page on the form that is opened in the client runner and not the whole DOM.

[Ankur Bawiskar · Accepted solution]

@OMT 

that's what I mentioned

It's not always guaranteed that Custom UI step will retrieve the HTML element.

Even if it retrieves and passes, it can fail in future test runs

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[OMT]

Great!!