Skip to content
KiweelyKiweelyKiweely

Build a Workday UI Test Charter an AI Agent Can Run Without Brittle CSS

Goal-driven UI charters survive Workday UI churn better than CSS selectors. Specify persona, task, and data readback; use Start Proxy in non-Production.

  • Checked against Workday on
  • Applies to Workday Extend
  • 1 min read
  • Published
  • By Kiweely
On this page

Selector-based click scripts break when Workday changes the browser UI. A charter an AI browser agent can execute should name business goals and evidence, not CSS paths.

Charter template

  1. Environment — Implementation / Sandbox / Preview (never imply Production proxy).
  2. Persona — Start Proxy as employee / manager / other unconstrained test user allowed by policy.
  3. Preconditions — app deployed (not only App Preview); test worker eligible for the process.
  4. Goal — “Submit time off for next Tuesday and see the event In Progress,” not “click div.xyz.”
  5. Readback — report, My Tasks, or business object fields that must match after the UI step.
  6. Stop conditions — security error, wrong tenant URL pattern, unexpected Production host.

Why Preview is called out

Workday documents App Preview differences (UTC-only, en-US-only, securityDomains ignored when disconnected, widgets that error). A charter that only passes in Preview is incomplete.

Honesty limit

Workday does not publish a standard “AI UI charter” format. This template exists so agents and humans share the same proof bar.

Sources checked

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.