- Home
- Skills
- Testing & Debugging
- acceptance-testing
Works with the AI Agents you already use
Acceptance Testing 2
Transform business requirements and process models into ISTQB-compliant acceptance tests and Gherkin scenarios.
$6
acceptance-testing
Example session with this skill installed
Review these acceptance criteria for the 'User Registration' story:
- User can sign up with email.
- Password must be strong.
- System sends a welcome email. Generate a scenario matrix.
- Read your context and instructions
- Compiled the acceptance-testing
I have reviewed the acceptance criteria for 'User Registration' and derived a scenario matrix focused on business outcomes.
Acceptance Testing Artifacts
Criterion Review Table
| Req/AC ID | Business outcome | Testability | Gap/question |
|---|---|---|---|
| AC 01 | Identity established via email | High | None |
| AC 02 | Account security | Low | 'Strong' is not measurable. Define length/complexity. |
| AC 03 | User onboarding communication | Medium | Trigger point and timing not specified. |
Scenario Matrix
| Scenario ID | Process/rule/path | Risk | Preconditions/data | Steps | Expected business outcome | Evidence | Status |
|---|---|---|---|---|---|---|---|
| SC_REG_01 | Happy Path | Low | Valid email, defined 'strong' password | Submit registration form | Account created; welcome email sent | DB Record, SMTP Log | Draft |
| SC_REG_02 | Duplicate Email | Med | Existing user email | Attempt registration with same email | Error message shown; no second account | UI Screenshot | Draft |
| SC_REG_03 | Weak Password | High | Password < 8 chars | Attempt registration with weak pass | Validation error; registration blocked | UI Trace | Draft |
BDD Scenarios (Gherkin)
Feature: User Registration
As a new visitor
I want to create an account
So that I can access personalized features
Scenario: Successful registration with valid details
Given the registration page is accessible
And the user "test@example.com" does not exist
When the user submits a valid email and a strong password
Then a new account should be created for "test@example.com"
And a welcome email should be dispatched to the user
Next steps
- Define measurable parameters for a "strong" password (e.g., length, character types).
- Confirm the SMTP server details for the welcome email verification.
- Approve the scenario matrix to begin test data preparation.
Connects securely to your tools. The creator never sees your data.
About this skill
Acceptance criteria often lack the precision needed for automated testing or formal sign-off. This skill bridges the gap between vague business requirements and verifiable test scenarios, ensuring every user story is testable and linked to a business outcome.
What it does
- Requirement Analysis reviews acceptance criteria for atomicity and measurability while identifying gaps or hidden assumptions.
- Scenario Derivation uses black-box techniques like boundary value analysis and decision tables to generate comprehensive test cases.
- Process Modeling maps BPMN and DMN models to specific test paths to ensure business logic is fully exercised.
- Artifact Creation generates living documentation in ATDD/BDD Gherkin format, focusing on business outcomes rather than UI implementation.
- Execution Planning defines the environment, test data, and participant roles required for UAT, alpha, or beta testing phases.
How it works
- Source Input starts by processing your requirements, business goals, and any existing process models or rules.
- Criteria Review checks supplied criteria against ISTQB standards to ensure they are true/false testable and atomic.
- Technique Selection applies risk-based prioritization and black-box modeling to derive a scenario matrix.
- Non-functional Mapping incorporates usability, performance, and security goals into the acceptance suite.
Frameworks & tools
This skill follows ISTQB CT-AcT, CTFL, and CTAL-AT standards. It works with Gherkin (Cucumber/SpecFlow), BPMN 2.0, and DMN modeling conventions for business process and rule testing.
Why this beats prompting it yourself
Generic prompts often produce tests focused on UI interactions like "clicks" and "inputs" instead of business value. This skill strictly enforces ISTQB-compliant acceptance techniques, preventing the invention of business rules and ensuring traceable coverage of process models.
Use cases
- Transform raw user stories into a structured BDD Gherkin scenario matrix.
- Audit existing acceptance criteria for testability and business alignment before a sprint starts.
- Map complex BPMN business workflows to a set of verifiable UAT test paths.
- Prepare a formal acceptance plan for regulatory or contractual sign-off.
Known limitations
Does not provide legal advice for regulatory compliance. Requires a user-specified writable folder for saving artifacts. Business rules must be supplied as it will not invent model behavior.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.
Requires user-specified folder for file output. Will not invent business rules or model behavior. Not a substitute for legal/compliance sign-off. Best for ISTQB-aligned workflows.
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 buying a skill.
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 2 days ago