The fragility of direct automation

Most UI automation efforts fail not because automation is hard, but because intent is trapped inside tools.

  • User expectations
  • Workflow assumptions
  • Acceptance criteria

When tools change, intent is lost.

Intent deserves a first‑class representation

  • Implicit
  • Hard‑coded
  • Tool‑specific

It must be explicit, reviewable, stable, and executable.

Why a contract matters

What the user expects
from
How automation achieves it

Without this separation:

  • Journeys drift
  • Maintenance cost rises
  • Confidence erodes

Why XML is well suited to intent

  • Structurally rigorous
  • Human‑readable
  • Universally supported
  • Tool‑agnostic
  • Schema‑validatable

Most importantly, it is boring in the best possible way.

XML as an intent boundary

  • A canonical representation of user intent
  • A stable interface between humans and automation
  • A point where validation, enrichment, and tooling can occur safely

Execution engines may change. Intent must not.

Avoiding the usual trap

  • Locators
  • Selectors
  • Automation instructions

It must express: Actions, Targets, Expectations.

The long‑term benefit

  • Users retain ownership
  • Tooling becomes replaceable
  • Automation becomes a service, not a dependency
  • Acceptance evidence becomes durable

Intent outlives tools.

Closing thought

In an ecosystem where software changes constantly, the most valuable artefact is not code — it is understood intent that can be re‑verified at will.

That is what an intent contract enables.


Where VerityJX™ fits

VerityJX™ operationalises verifiable journeys by preserving user intent in a neutral contract and enabling those journeys to be executed — manually or automatically — against real systems, producing evidence a software consumer can own.

Read: Why VerityJX™ exists →

Related insights

This article is part of a broader set of perspectives on acceptance, user journeys, and verification in vendor-supplied software.

Browse all insights →

About the author

This article reflects the thinking behind VerityJX™ by UJX (User Journey eXplorer), focused on helping organisations verify the user journeys they depend on — even when they don’t own the software.