Get a first look at what's coming. The Developer Passport Australia Release Preview kicks off March 12. Dive in! 

ATF on Australia upgrade failed because of client script not run on the Client Test Runner

SanHuynh
Tera Contributor

I am currently on glide-australia-02-11-2026__patch0-hotfix1-03-16-2026 and have been running some ATF tests that involve Client Scripts to set field mandatory and visibility.

However, when the ATF runs using the Client Test Runner, the Client Script does not execute even when the trigger conditions are met.

When I manually retest the same scenario, the Client Script runs as expected.

Do anyone have this kind of issue?

#ATF #Australia

3 REPLIES 3

Tanushree Maiti
Tera Sage

Hi @SanHuynh 

 

Can you repair ATF related plugins and try again.

  Incident Management — ATF Tests plugin (com.snc.incident.atf)

ATF Test Generator and Cloud Runner: com.glide.automated_testing_framework.
Automated Testing for Virtual Agent: com.glide.cs.atf.
Incident Management — ATF Tests: com.snc.incident.atf.
Problem Management — ATF Tests: com.snc.problem.atf.
Change Management - ATF Tests: com.snc.change_management.atf

 

Also you can refer:

KB0692103 ATF test failing due to a client-side JavaScript error 

 

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:

SanHuynh
Tera Contributor

For the KB, we currently using a simple client script to just show mandatory/hide specific dictionary fields on the the INC form, for example. So that KB is mostly not relevant to the current issue.

I have tried to repair the plugin related to ATF and related to the module we're currently testing (com.glide.automated_testing_framework and com.snc.incident.atf), but it still doesn't run the expected client script in the Client Test Runner.

We only just found out about this issue when observe the Client Test Runner and no error logs is producing at the moment.

SanHuynh
Tera Contributor

This also seem like affected to UI Policies, even though the UI Policies in questions are within correct conditions and running normally in manual run.