- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2020 01:53 PM
I'm experiencing errors when run Click a UI Action in a ATF test. I have tried to recreate the step but without success.
Anyone have any idea why i'm getting the following error:
This step failed because the client error 'Error: [$parse:syntax] http://errors.angularjs.org/1.5.11/$parse/syntax?p0=%7B&p1=invalid%20key&p2=2&p3=%7B%7B%3A%3AtrustAsHtml(change.sanitized_new_value)%7D%7D&p4=%7B%3A%3AtrustAsHtml(change.sanitized_new_value)%7D%7D
at https://upsqa.service-now.com/scripts/js_includes_ui16_form.jsx?v=12-03-2019_1915&lp=Mon_Jan_13_14_22_18_PST_2020&c=19_479:9:426
at throwError (https://upsqa.service-now.com/scripts/js_includes_ui16_form.jsx?v=12-03-2019_1915&lp=Mon_Jan_13_14_22_18_PST_2020&c=19_479:236:200)
at t.object (https://upsqa.service-now.com/scripts/js_includes_ui16_form.jsx?v=12-03-2019_1915&lp=Mon_Jan_13_14_22_18_PST_2020&c=19_479:236:33)
at t.primary (https://upsqa.service-now.com/scripts/js_includes_ui16_form.jsx?v=12-03-2019_1915&lp=Mon_Jan_13_14_22_18_PST_2020&c=19_479:232:151)
at t.unary (https://upsqa.service-now.com/scripts/js_includes_ui16_form.jsx?v=12-03-2019_1915&lp=Mon_Jan_13_14_22_18_PST_2020&c=19_479:231:503)
at t.multiplicative (https://upsqa.service-now.com/scripts/js_includes_ui16_form.jsx?v=12-03-2019_1915&lp=Mon_Jan_13_14_22_18_PST_2020&c=19_479:231:249)
at t.additive (https://upsqa.service-now.com/scripts/js_includes_ui16_form.jsx?v=12-03-2019_1915&lp=Mon_Jan_13_14_22_18_PST_2020&c=19_479:231:76)
at t.relational (https://upsqa.service-now.com/scripts/js_includes_ui16_form.jsx?v=12-03-2019_1915&lp=Mon_Jan_13_14_22_18_PST_2020&c=19_479:230:416)
at t.equality (https://upsqa.service-now.com/scripts/js_includes_ui16_form.jsx?v=12-03-2019_1915&lp=Mon_Jan_13_14_22_18_PST_2020&c=19_479:230:241)
at t.logicalAND (https://upsqa.service-now.com/scripts/js_includes_ui16_form.jsx?v=12-03-2019_1915&lp=Mon_Jan_13_14_22_18_PST_2020&c=19_479:230:94)' 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.
Solved! Go to Solution.
- Labels:
-
Platform and Cloud Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2020 08:08 PM
Hi,
Have you opened the form using open existing record step?
Also is that UI action visible to the user with whose session you are running ATF?
Also you can ignore the error by adding it to whitelist error
https://docs.servicenow.com/bundle/newyork-application-development/page/administer/auto-test-framework/reference/whitelisted-client-errors.html
Mark ✅ Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
Thanks
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2020 08:08 PM
Hi,
Have you opened the form using open existing record step?
Also is that UI action visible to the user with whose session you are running ATF?
Also you can ignore the error by adding it to whitelist error
https://docs.servicenow.com/bundle/newyork-application-development/page/administer/auto-test-framework/reference/whitelisted-client-errors.html
Mark ✅ Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
Thanks
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2020 04:52 AM
Thanks for taking a look.
Yes to all your questions with the exception of adding it to the whitelist. Trying to figure out where the error is coming from and what is causing it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2020 12:37 PM
I tested with a different workstation and could not reproduce the this error so, I believe it was something with my laptop configuration. I whitelisted the error and continued the test.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2020 12:39 PM
Are you using a different browser/os or different versions of the browser/os? These could have an impact when running your tests.