Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for systems analysts

Acceptance Test Scenario Agent

A scenario set that covers every requirement and real workflow, with every failure retested

Acceptance Test Scenario Agent: what goes in, what the agent does and what you get

What it does

Acceptance tests often follow the requirements list and miss how people really work, such as returning to an old record or switching between screens. This agent reads the requirements and process maps and builds step-by-step scenarios that follow real workflows, including unusual paths. It maps each scenario to the requirements it covers and checks coverage, listing requirements with no scenario. It drafts new scenarios to fill gaps and checks the map again. During testing, it reads results from the test log. For each failure it reopens the linked requirement, groups failures by cause and drafts a retest scenario once the fix is delivered. It keeps going until all scenarios pass or are accepted as known issues. The analyst approves the set and the closure. Edge case: a requirement is covered only by a happy path.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueApprovedYes, continueApprovedNoNo 1 STARTS WHEN Requirements are signed off for acceptance testing 2 USES A TOOL Read requirements and process maps 3 DOES Build scenarios for each workflow, including unusualpaths 4 DOES Map scenarios to requirements 5 CHECKS THE RESULT Is every requirement covered by at least onescenario? If not: draft new scenarios for each uncoveredrequirement. Back to step 4. 6 YOU APPROVE Analyst approves the scenario set 7 USES A TOOL Read test results as testers log them 8 CHECKS THE RESULT Did every scenario pass? If not: reopen the linked requirement and group failuresby cause. Back to step 7. 9 USES A TOOL Rerun retest scenarios for each delivered fix andupdate results 10 YOU APPROVE Analyst approves closure or accepted known issues 11 RESULT Test coverage and results report
Read the steps as a list
  1. Requirements are signed off for acceptance testing
  2. Read requirements and process maps
  3. Build scenarios for each workflow, including unusual paths
  4. Map scenarios to requirements
  5. Is every requirement covered by at least one scenario?If not: draft new scenarios for each uncovered requirement. Back to step 4.
  6. Analyst approves the scenario setThe agent waits here for your OK.
  7. Read test results as testers log them
  8. Did every scenario pass?If not: reopen the linked requirement and group failures by cause. Back to step 7.
  9. Rerun retest scenarios for each delivered fix and update results
  10. Analyst approves closure or accepted known issuesThe agent waits here for your OK.
  11. Test coverage and results report

How it decides

Coverage counts only if a scenario exercises the requirement, including at least one unusual path for important ones.

  • Add an unusual-path scenario for every high-priority requirement
  • Reopen a requirement when any linked scenario fails
  • Group failures with the same cause
  • Treat requirements covered only by a happy path as partly covered

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Priority levels needing unusual paths
  • Scenario format
  • Test log source
  • Roles included

What keeps you in control

It always asks you first

  • Final scenario set
  • Closure of failed items

Hard limits

  • Never edits the requirements
  • Never marks a test as passed

It stops when

  • Done: all requirements covered and scenarios passed or accepted
  • Stop: requirements change during testing and need review

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensFor a claims system, the agent built 48 scenarios and found 5 of 62 requirements uncovered, including claim reopening. It drafted 6 more scenarios. In testing, 4 failed, 3 from one payment screen bug. It reopened the requirement and wrote a retest after the fix. All scenarios passed on the second round, and the analyst approved closure with one known issue.

More agents for systems analysts