ServiceNow Ships Twice A Year. Your Test Suite Shouldn't Break Twice A Year.
AI agents that test ITSM, HRSD, CSM and your custom apps by intent instead of selectors — so a family release, a patch, or a runtime-generated element ID stops being a testing project.
Zurich
Last of the city names
Australia
First country name · current
Brazil
Next family release
Canada
Then Denmark
Your Regression Cycle Is Scheduled By Someone Else
Two family releases a year, patches every four to six weeks, and an N-1 policy that makes upgrading non-optional.
Two Forced Releases A Year
Australia went GA on 5 May 2026 and Brazil lands in Q4. The N-1 policy means you are never more than one family behind, so the regression cycle is scheduled for you — with cutoff windows concentrated in June and December.
Element IDs That Move
ServiceNow generates much of its UI at runtime. Selector-based scripts pinned to dynamic IDs, nested iframes, and shadow DOM break on the release calendar, not when your code changes.
Patches Every Four To Six Weeks
Regression is not a twice-yearly event. Every patch inside a family is another pass, and Instance Audit treats an outdated patch level as a finding even on a supported release.
Journeys That Leave The Platform
A catalog request that ends in an ERP purchase order, an SSO handoff, a confirmation email. The business process crosses the platform edge even when your test coverage stops at it.
Tests That Describe Intent, Not Selectors
TestZeus agents read your instance the way a tester does. There is no XPath pinned to a runtime-generated ID, so there is nothing for a family release to break — and the journey does not have to stop at the platform edge.
Three Things Generic Test Automation Cannot Do Here
Release-Proof By Architecture, Not By Repair
Self-healing repairs a broken selector after it breaks. TestZeus agents never bind to one. They read the interface the way your tester does — by intent — so a workflow described as "submit a hardware request and approve it as the manager" survives Australia, Brazil and every patch between.
Coverage That Continues Past The Platform Edge
ATF validates what happens inside ServiceNow. Your business process does not stop there. TestZeus agents follow one journey from a catalog item through the ERP, the approval email and the API layer beneath, and assert on all of it in a single test.
Written In ServiceNow's Own Vocabulary
Your BAs and platform owners write tests in plain English, and the agents already know what a catalog item, an approval chain, an ACL and an impersonation are. No scripting resource, no step-by-step designer, no line-by-line assembly of hundreds of tests.
Into Your Instances, Out To Your Pipeline
ATF stays as your in-platform baseline. TestZeus covers the UI layer, cross-browser execution, and everything past the platform edge — with video and network logs captured on every run.
ATF, Scripts, Or Agents
| ServiceNow ATF | Selector-based tools | TestZeus agents | |
|---|---|---|---|
| Cost | Included in platform | Licensed | Licensed |
| Inside-platform logic | Strong | Partial | Strong |
| Survives a family release | Upgrade-aware | Needs repair | No selectors to break |
| Past the platform edge | No | Sometimes | Yes |
| Runs on production | Disabled by default | Yes | Yes |
| Authoring | Step-by-step designer | Code or record | Plain English |
See It Run On Your Own Instance
Bring one workflow that breaks every release. We will build it as an agent test and run it against your upgrade preview instance.
Frequently Asked Questions
Yes. ServiceNow ships the Automated Test Framework (ATF) with the platform at no extra cost, and it is the sensible baseline for any programme. ATF is upgrade-aware, strong on server-side logic such as business rules and ACLs, and includes Quick Start Tests for sanity-checking an instance after an upgrade. It runs against sub-production instances, as it is disabled on production by default.
ATF's boundary is the platform edge: it validates what happens inside ServiceNow, not a journey that continues into an ERP, a payment provider or an SSO handoff. It also offers no self-healing and limited cross-browser and mobile coverage, and at scale, assembling tests step by step in the designer becomes the bottleneck. Workspace coverage has improved — the Zurich release added native ATF support for Configurable Workspaces along with a page inspector for authoring — though Next Experience support arrives component by component, so check the release notes for your version. Most teams run ATF as the baseline and add a second tool for everything past that line.
Run your automated regression suite against the upgrade preview instance before committing the upgrade, and pair it with a skipped-record review. Practitioners consistently report that the largest upgrade risks come from skipped records and customization conflicts rather than UI changes alone, so test automation and skipped-record analysis are complementary, not alternatives. Under the N-1 policy you have two of these cycles a year, with cutoff windows concentrated in June and December.
As of August 2026 the current family release is Australia, which reached general availability on 5 May 2026. It is the first country-named release after the city-name sequence ended with Zurich in September 2025. Brazil is expected in Q4 2026, followed by Canada and Denmark. ServiceNow now targets general availability in Q2 and Q4, replacing the earlier Q1/Q3 pattern, and ships patches every four to six weeks within a family.
With TestZeus, yes. A single test can raise a catalog request in ServiceNow, verify the resulting purchase order in your ERP, and confirm the notification email — asserting at each step, across UI and API layers. This is the main coverage gap left by platform-native tooling, because ATF by design does not follow a process outside the Now Platform.
No. TestZeus tests are written in plain English and executed by AI agents that already understand ServiceNow concepts such as catalog items, approval chains, ACLs and impersonation. There are no selectors, XPaths or object IDs to author or maintain, which means platform owners and business analysts can build and read the suite without a scripting resource.
No, and we would not recommend it. ATF is free, native, upgrade-aware and genuinely good at server-side validation, so ripping it out costs you coverage you already have. TestZeus is designed to sit alongside it and cover what ATF cannot: UI-layer regression on modern interfaces, cross-browser execution, and end-to-end journeys that leave the platform.
It depends on suite size and how much runs in parallel, but the practical target during an upgrade window is a full regression pass inside the maintenance window rather than across several days. Because TestZeus agents do not require selector repair after a family release, the time normally lost to fixing broken scripts before a run disappears from the critical path.
Stop Rebuilding Your Suite Every Family Release
Brazil lands in Q4. Be ready before the June and December windows.
