GeneWorks product suite
geneworks verify

Deliver with confidence.

Verify tests every change two ways and captures the evidence as it runs. GeneWorks owns the runner for both, so proving the work does not depend on additional ServiceNow licensing or on pulling business users off their day jobs.

Point Verify at a change Read the documentation
Functional test · incident formbrowser-driven · no human
launching browser sessionok
logging in as service accountok
navigating to incident.formok
filling mandatory fieldsok
capturing evidencescreenshot 4/4
resultPASS
All assertions green, evidence attached to the story. A failing test is never reported as passed.
70–90%
target reduction in testing and UAT effort
No license
ServiceNow CloudRunner is not required
Every step
screenshot evidence captured as the test runs
Why this is the flagship

Acceleration usually stops at the point where someone has to prove the work is correct.

Testing and UAT are where timelines slip, where business users get pulled off their day jobs for a fortnight, and where audit evidence gets assembled by hand after the fact.

Verify moves proof into the run itself. The evidence exists at the moment of sign-off because producing it was part of doing the work — not a separate project that starts once the build is done.

0CloudRunner licenses

ATF Test Center

ServiceNow's Automated Test Framework, server and client suites, authored alongside the build and executed on the GeneWorks runner. No ServiceNow CloudRunner license is required.

  • Authored with the code — suites are written at build time, so coverage tracks the change rather than trailing it.
  • Server and client — record-level assertions and form-level behaviour, including guards and negative cases.
  • Stored in your instance — you own the tests, and they stay useful whether or not you continue with GeneWorks.
ATF suite · CH-001server + client
VIP auto-prioritisepass
guard: non-VIP unchangedpass
work note writtenpass
priority survives lookuppass
written tosys_atf_* (yours)
Suites live in your instance. Portable, and yours to keep.
4/4steps evidenced
Self-healingknown-pattern failures
failure detectedselector drift
repair attemptedFix FT · 1 click
re-runpass
unrepairableflagged to a human
Every failure writes to a lessons-learned record the agents read before acting. Repeat failures on your instance decline over time.

Functional Test

The part that replaces manual UAT. An agent opens a real browser, logs in with the service account, navigates to the relevant form, fills the mandatory fields, and captures screenshot evidence at each step.

It is indistinguishable from a human tester, except that it does not get tired, does not skip the negative case, and does not mark a failing test as passed to keep a release date.

1package, not scattered files

The evidence package

Verification is the second of the two human gates. What you review is a single assembled package, available the moment the run finishes.

  • ATF results — server and client suites, pass and fail state per assertion.
  • Functional screenshots — step-by-step visual evidence of the browser run.
  • Execution logs — what ran, when, against which instance.
  • The named, scoped update set the change is packaged in.

Because the evidence is produced by the run rather than assembled afterwards, it suits control frameworks that require documented test evidence.

Audit recordwritten per action
entitycreated / modified / deleted
timestampISO-8601
responsible agentnamed
risk levelscored
statebefore and after
Two independent trails: the platform's own append-only records and your instance's native sys_audit.
Governance

A failing test is never reported as passed.

Test results are not overwritten and outcomes are not softened to hit a date. Verification is a human gate: a named reviewer signs off on the evidence package before the change closes, and nothing reaches your change advisory board unseen.

Can
Cannot
Write and run ATF and functional tests
Mark a failing test as passed
Repair known-pattern failures and re-run
Retry an unknown failure silently
Assemble and present the evidence package
Close a change without a named sign-off
One engine. Five products.
Design
Map the instance. Plan the change.
Build
Approved design to working configuration.
Verify
ATF and browser tests, with the evidence.
Optimize
Score catalog, CMDB, data and upgrades.
Ask Gene
Ask the instance anything, in plain English.

Bring a change you have already built.

Let Verify generate the ATF suite and the functional evidence package against work you can already judge for yourself.

Point Verify at a change
No plugin · no MID Server · no install in your environment