What is VerityJX™
Verifiable Journey Execution for acceptance testing of vendor-supplied software
A precise definition
VerityJX™ is a user-centred Journey Execution pattern for UI acceptance testing of vendor-supplied web software.
It enables organisations to define the real-world user journeys they rely on, represent those journeys in a neutral, structured XML format, and verify them — manually or automatically — against live systems, producing outcomes understandable by business users and consumable by systems.
Important: journeys do not have to “end up in automation”. VerityJX™ is equally effective as a way to map, document, standardise, and evidence critical journeys — and to move to automation only when you choose.
VerityJX™ is inspired by Behaviour-Driven Development principles, but is deliberately designed for environments where organisations do not own the application code, do not control vendor testing, and do not maintain a dedicated QA function.
The problem VerityJX™ addresses
Most modern organisations depend on SaaS or vendor-supplied web applications for critical daily operations.
When those vendors release updates:
- • The organisation does not control what was tested
- • The organisation cannot rely on unit or integration tests it does not own
- • The organisation still carries the operational and business risk
Traditional testing approaches assume:
- • Access to source code
- • Developer-authored tests
- • Long-lived QA teams
- • Coverage-driven metrics
These assumptions do not hold for software consumers.
The result is an acceptance gap: a lack of reliable assurance that the user journeys the organisation depends on still function after each vendor release.
VerityJX™ exists to close that gap.
What VerityJX™ is — and is not
VerityJX™ is
- • A pattern, not a single tool
- • Focused on UI acceptance
- • User-authored, not developer-authored
- • Centred on journeys, not test cases
- • Designed for vendor-supplied software
- • Useful for documenting and standardising manual acceptance
- • Compatible with automation tools such as Selenium
VerityJX™ is not
- • A unit testing framework
- • A replacement for vendor QA
- • A coverage-driven testing approach
- • A scripting language for automation engineers
- • A requirement to adopt BDD tooling or syntax
- • A requirement to automate journeys before they are useful
VerityJX™ applies BDD thinking to acceptance where unit tests cannot exist — and keeps the journey definition useful even before automation.
What “JX” means
JX stands for Verifiable Journey Execution.
- • A journey is an end-to-end flow as experienced by a real user
- • Execution can be manual or automated, but is designed to be repeatable
- • Verification produces evidence meaningful to humans and systems
Journeys — not tests — are the unit of acceptance.
How VerityJX™ works (conceptually)
VerityJX™ follows a deliberately simple and extensible model:
1. Users define journeys
Business users describe what they actually do in the application — using structured, plain-language tools they already know.
- • Real workflows
- • Meaningful outcomes
- • Human comprehension
- • No testing syntax required
2. Journeys become intent XML
User-defined journeys are transformed into a neutral XML representation that acts as the canonical contract.
- • Preserves user intent
- • Structured and reviewable
- • Independent of execution framework
- • Easy to index, search, and tag
In VerityJX™, XML is not an implementation detail — it is the intent boundary.
3. Journeys are useful immediately (even without automation)
The same intent XML can standardise manual acceptance and preserve organisational knowledge.
- • Repeatable manual execution guides
- • Consistent evidence capture expectations
- • Journey libraries that survive staff turnover
- • A single source of truth for “what matters”
4. Automation becomes an option (when you’re ready)
When appropriate, the intent XML can drive automated UI execution using tools such as Selenium and WebDriver.
- • On demand
- • On a schedule
- • In response to vendor releases
5. Outcomes provide acceptance confidence
Results are reported at the journey level, understandable by non-technical stakeholders, and suitable for dashboards, alerts, audits, or downstream systems.
Why XML is central to VerityJX™
XML is the canonical format because it turns journeys into durable organisational assets — not transient test scripts.
Structured & reviewable
Journeys have a consistent shape that can be validated, diffed, and peer-reviewed.
Easily indexed & searchable
A journey library can be queried by system area, risk, persona, outcome, vendor module, and more.
Portable over time
Tools change. Vendors change. Your journey definitions remain readable and transferrable.
Transformable
The same journeys can be transformed into manuals, evidence packs, automation, reports, or new execution engines.
Execution tools may change.
Journeys must not.
Relationship to Behaviour-Driven Development
VerityJX™ is philosophically aligned with BDD but operationally distinct.
| Aspect | BDD | VerityJX™ |
|---|---|---|
| Primary audience | Developers / testers | Business & operations |
| Authoring style | Scenarios | Journeys |
| Canonical format | Feature files / code | Intent XML |
| Typical scope | Unit to integration | UI acceptance |
| Code ownership assumed | Yes | No |
| Primary goal | Build the right thing | Ensure it still works |
VerityJX™ embraces shared understanding and behaviour-focused thinking, while recognising the realities faced by organisations that consume — rather than build — software.
Who should use VerityJX™
VerityJX™ is suited to organisations that:
- • Depend on vendor-supplied or SaaS web applications
- • Have critical daily user workflows
- • Need manual acceptance to be consistent and evidence-friendly
- • Cannot rely on internal unit or integration tests
- • Lack a full-time QA or test automation team
- • Want the option to automate later without rewriting journeys
If your organisation does not own the code — but owns the consequences — VerityJX™ is designed for you.
Developed by UJX
UJX (User Journey eXplorer) focuses on helping organisations express, understand, and validate the journeys they depend on.
VerityJX™ is the practical expression of that mission: turning user journeys into durable definitions that can be documented, reused, and executed — producing acceptance confidence a software consumer can own.