Automated Test Framework- Test cases are getting failed due to glide.ui.polaris.ais client error

kajol Kumari
Tera Contributor

I am in tokyo version. This step result appears only on a step that interacts with the UI.

 

 

 

This step failed because the client error 'The searchContexts do not match the glide.ui.polaris.ais_ready value. Please update system properties ' was detected on the page being tested. See failing Test Logs. To ignore these errors in the next test run, use 'Add all client errors to warning/ignored list' links.

 

I am new to ATF.

any suggestions on how to fix this error?

 

Thank you

Thank you

12 REPLIES 12

ray33
Tera Contributor

Yet another work-around referring to a locked down problem ticket.

 

We can't tell you why AI is making errors because that is a secret. In fact, it might be so secret that AI won't even tell us, but you can ignore the AI errors like this....  

Does AI do anything but replace existing features with unstable and inconsistent and incomplete version of the same functionality with an AI prefix that can be mentioned on investor calls?

 

Maybe it stands for Artificial Incompetence. Instead of hiring incompetent people to break everything, you can enable Artificial Incompetence and let the robots break things faster / free. 

Meroda Gezahegn
Tera Contributor

I am in Vancouver release working on ATF test The navigation part application menu and module  but the error is still   and it says 

'This step failed because the client error 'The searchContexts do not match the glide.ui.polaris.ais_ready value. Please update system properties ' was detected on the page being tested. See failing Test Logs. To ignore these errors in the next test run, use 'Add all client errors to warning/ignored list' links.'

'The searchContexts do not match the glide.ui.polaris.ais_ready value. Please update system properties'

I have managed to see that adding the itil role to the user that is impersonated at the time when the step which is showing this error, is executed, prevent showing this error. I was trying to add roles to the user that are inherited with the itil, but it did not help, so I guess the itil as itself is important here. But did not manage to investigate what stands behind that behavior.