Week 4 of 8
ATF: where it fits
The Automated Test Framework is the first tool most ServiceNow teams reach for, and it is good at a lot: server-side logic, classic forms and lists, catalog items and flows, with test data rolled back after each run. The ATF Test Generator and Cloud Runner Store app can generate tests and run them on a ServiceNow-hosted browser.
It has limits you should plan around. ATF does not support Next Experience components such as UI Builder pages. Results are deleted after 30 days by default. And ServiceNow positions it for non-production instances only.
This week: inventory your ATF suite and mark the gaps
- List every ATF test and suite with its application, module, owner and the runner it needs (client, scheduled or Cloud Runner).
- Flag tests that run as admin. They prove the logic, not the access. Add impersonation steps for real roles.
- Mark every critical process that lives in a UI Builder Workspace or portal page. Those need another approach.
- Turn on result retention, or export suite results for each upgrade, so your sign-off evidence outlives the 30-day purge.
- Retire or fix flaky tests now. A suite nobody trusts gets skipped in the upgrade week.
Number of the week
30 days
is how long ATF keeps test and suite results by default. Upgrade evidence needs to live somewhere longer.
Source: ServiceNow docs, Exploring Automated Test Framework (Zurich)Use this week
- ServiceNow ATF Suite Coverage & Maintenance Tracker →
Every test with runner, role, last result and flakiness, plus process coverage that flags UI Builder gaps.
- Regression Automation Prioritization Scorecard →
Rank what to automate next by risk, change and frequency.
Next week: tests that run as admin prove nothing about access. We build the role and ACL matrix.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.