On the running the test of ATF error is coming

Community Alums · ‎09-25-2023

Hi Everyone,

I have created a ATF having two different test under test suite. When I run the test suite
(i) At the time of running 1st test---It ran successfully
(ii) At the time of running 2nd test--It failed

Error---This step failed because the client error 'TypeError: Cannot read properties of null (reading 'hopscotch')' 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 have not used any JavaScript in the ATF.
Please provide me some solution so that the ATF can be run smoothly.

Thanks & Regards
Utsav

Shaqeel · ‎09-25-2023

Hi @Community Alums

Just ignore the error and run.

Steps:

Open the test result.

ignore the error from Related Links.

Run the test again.

Regrds

Shaqeel

***********************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting "Accept as Solution" and " Helpful." This action benefits both the community and me.

***********************************************************************************************************************

Regards

Shaqeel

View solution in original post

Ankur Bawiskar · ‎09-25-2023

@Community Alums

It's available on docs as well

How to use the Client Error Inclusion list in the Automated Test Framework

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

View solution in original post

Dave Becker · ‎02-05-2024

We have the exact same issue in our DEV instance after a clone. Same error. We have already added the error to the whitelist per the steps (open test result, ignore error from related list, validate whitelist has the entry set to True). However, this did not resolve the issue. We also did a repair on "hopscotsh" plugin and re-ran the tests which still threw the same error. We have a case open for this now.