Test User Data Matrix
Define the synthetic test users, roles, permissions, seeded data, edge cases, and reset requirements a test effort needs.
Sample result
How it works
What Test User Data Matrix does
Builds a persona list across role, tenant, account state, and plan; a role-by-resource-by-action permission matrix with allow, deny, own-record, and conditional expectations; negative and cross-tenant cases; a seed catalogue with volume, boundary, date, money, and text edge data; and a reset and isolation plan covering parallel runs and side effects, with case counts computed.
Use it when
Someone asks which test users and roles to create, how to test permissions, what seed data and edge cases to prepare, or how to reset data between test runs.
Use something else for
The overall test strategy, running browser tests, accessibility checks, or the release verdict.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
Persona table, permission matrix, seed data catalogue and reset plan
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Test User Data Matrix
Updated Oct 20, 2026.
What does Test User Data Matrix do?
Define the synthetic test users, roles, permissions, seeded data, edge cases, and reset requirements a test effort needs. Builds a persona list across role, tenant, account state, and plan; a role-by-resource-by-action permission matrix with allow, deny, own-record, and conditional expectations; negative and cross-tenant cases; a seed catalogue with volume, boundary, date, money, and text edge data; and a reset and isolation plan covering parallel runs and side effects, with case counts computed. Use when someone asks which test users and roles to create, how to test permissions, what seed data and edge cases to prepare, or how to reset data between test runs. Do not use for the overall test strategy (use test-plan), running browser tests (use playwright-browser-runner), accessibility checks (use accessibility-qa), or the release verdict (use release-regression-report).
Who is Test User Data Matrix for?
It is designed for QA engineers, test automation developers, security reviewers and platform engineers.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Test User Data Matrix produce?
Persona table, permission matrix, seed data catalogue and reset plan. Results come back with their sources and any open questions for you to check before anything is used.
How much does Test User Data Matrix cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgtan3h00bp…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Test User Data Matrix fits
Similar skills5
Accessibility Qa
Plan and report accessibility QA for a web or app experience against WCAG 2.2 level AA. Defines scope and a page and flow sample, combines automated scans with manual keyboard, screen reader, zoom and reflow, contrast, semantics, and form-error testing, computes contrast ratios, logs each issue with the success criterion, affected users, severity, and a fix direction, and ends with retest criteria. Use when someone asks for accessibility testing, an accessibility audit plan or report, keyboard or screen reader checks, contrast checks, or WCAG review of a page or flow. Do not use for the overall test plan (use test-plan), the release verdict (use release-regression-report), visual design critique (use design-audit), or posting issue text (use jira-evidence-uploader).FreeSkill · Product and engineeringdiagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.FreeSkill · Product and engineeringgrilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.FreeCommunitySkill · Product and engineeringJira Evidence Uploader
Package QA findings into Jira-ready drafts without posting anything. Normalizes each finding to one defect, decides new issue versus comment versus link, writes the summary, preconditions, numbered reproduction steps, expected and actual results, severity proposal, and environment block, selects and names screenshots, recordings, and log excerpts, runs a redaction check for personal data, builds an attachment manifest with hashes, and drafts new-issue, evidence, and retest comments. Use when someone asks to write up a bug for Jira, turn QA findings into tickets, package screenshots and reproduction steps, or draft evidence comments. Do not use for writing epics or stories (use jira-epic-writer), the release verdict (use release-regression-report), test planning (use test-plan), or running the tests (use playwright-browser-runner).FreeSkill · Product and engineeringPlaywright Browser Runner
Guide browser test execution with Playwright or a similar runner as a run plan the user carries out. Covers pre-flight checks, run modes (smoke, targeted, full, cross-browser, repeat for flake detection), command templates, evidence settings (trace, screenshot, video), a failure triage decision tree that separates product bugs from locator, data, environment, and flaky causes, repeat sizing, quarantine rules, and a stable run record for reporting. Use when someone asks how to run browser tests, capture evidence, triage Playwright failures, find flaky tests, or report a browser test run reliably. Do not use for the overall test strategy (use test-plan), the release verdict (use release-regression-report), accessibility checks (use accessibility-qa), or writing issue text (use jira-evidence-uploader).FreeHave a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.