UAT

Seeded Personas and Data

Understand the seeded users, roles, systems, and sample changes used for UAT and demos.

Why seeded data matters

Seeded data makes testing and demos repeatable. It ensures every tester starts from the same baseline and role behavior can be validated consistently.

Seeded personas

Typical personas include Owner, Admin, Submitter, Reviewer, Viewer, Finance Reviewer, Security Reviewer, Restricted Reviewer.

Seeded sample changes

Typical seeded records include high-risk pricing change, blocked billing logic change, approved revenue recognition change, restricted security change, overdue approval change, draft in progress.

How to use this data

Use the seeded personas and sample changes as the basis for UAT scripts, E2E tests, demos, and screenshot generation.

Seeded demo dataset
Seeded Changes Overview
A good seeded environment should contain realistic users and changes.
✏️ Edit this page on GitHub
Was this page helpful?
Send feedback