- Home
- Skills
- Workflow Automation
- Automation UAT fixture pack
Automation UAT fixture pack
For automation delivery teams: input fixtures with expected state transitions.
$12
Works with the AI Agents you already use
Automation UAT fixture pack
Example session with this skill installed
Use the skill to produce input fixtures with expected state transitions. Input S1: Workflow imports orders every hour. Reprocessing same order must update it, not create another. Test order X appears twice with corrected quantity 3.
- Read your context and instructions
- Compiled the automation uat fixture
Synthetic test example. Recorded AI smoke-test response. No real service changes were executed.
The destination must retain one order X and apply the corrected quantity 3. S1 establishes update-on-reprocessing; the initial quantity is missing.
Proposed UAT fixtures using an explicitly synthetic initial quantity of 1:
| Case | Initial state and hourly input | Expected destination | Evidence | Owner |
|---|---|---|---|---|
| First import | No X; input {id:"X",quantity:1} | One X with quantity 1 | Before/after row count and fields | Unknown |
| Correction | Existing X=1; next input {id:"X",quantity:3} | One X with quantity 3 | Same logical identity and row count 1 | Unknown |
| Exact replay | Existing X=3; replay {id:"X",quantity:3} | One X with quantity 3 | No duplicate | Unknown |
| Same-batch duplicate | X appears as 1 then 3 in one import | Proposed last-authoritative-version rule yields X=3, but ordering contract needs confirmation | Version/order log | Unknown |
| Recovery after write | Persist X=3, then simulate lost acknowledgment and replay | One X=3 | Destination snapshot and retry trace | Unknown |
Trigger: hourly import. Transformation: match source order identity, apply authoritative correction. Destination: existing record update rather than insert.
Missing inputs: source schema, identity mapping, version/order rule, retry semantics and owner. No import was executed.
Acceptance check: all confirmed-order replay paths leave exactly one X with quantity 3; out-of-order corrections need an agreed version rule.
Connects securely to your tools. The creator never sees your data.
About this skill
Use this skill when you have a workflow contract and acceptance requirements and need input fixtures with expected state transitions.
The workflow:
- Trace each acceptance rule through trigger, transformation and destination.
- Choose normal, boundary and recovery cases using synthetic inputs.
- Specify observable destination state and duplicate-handling behavior.
- Return a UAT table with evidence capture and owner fields left unknown if absent.
You receive the work product with input-linked findings, visible unknowns and concrete verification checks. Work from pasted or redacted text. This skill does not execute changes, send messages or access service accounts.
Original AI-assisted content. A synthetic worked example is included. Use through your Agensi-connected agent. No extra paid API or runtime is required for this workflow. Delivery is through the Agensi agent connection. No sales, ranking or compliance outcome is promised.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
Permissions
No special permissions declared or detected