acceptance-testing

Files (30)

• AGENTS.md
• README.md
• SKILL.md
• metadata.json
• _sections.md · rules/
• _template.md · rules/
• acceptance-testing-coupled-scenarios.md · rules/
• acceptance-testing-generate-html-reports-for-stakeholder-review-cucumber.md · rules/
• acceptance-testing-hold-three-amigos-sessions-business-dev-qa-before.md · rules/
• acceptance-testing-imperative-style.md · rules/
• acceptance-testing-incidental-details.md · rules/
• acceptance-testing-keep-scenarios-independent.md · rules/
• acceptance-testing-keep-step-definitions-thin.md · rules/
• acceptance-testing-limit-scenarios-to-3-8-steps-if-longer-consider-splitting.md · rules/
• acceptance-testing-parallelize-scenario-execution-where-frameworks-support-it.md · rules/
• acceptance-testing-reuse-step-definitions-across-features-avoid-duplicating.md · rules/
• acceptance-testing-run-acceptance-tests-in-ci-on-every-pr-for-critical-flows.md · rules/
• acceptance-testing-separate-fast-api-level-acceptance-tests-from-slow.md · rules/
• acceptance-testing-tag-scenarios-smoke-regression-wip-to-run-subsets-in.md · rules/
• acceptance-testing-testing-implementation.md · rules/
• acceptance-testing-too-many-scenarios.md · rules/
• acceptance-testing-treat-feature-files-as-living-documentation.md · rules/
• acceptance-testing-use-concrete-examples-with-real-data-not-abstract.md · rules/
• acceptance-testing-use-dedicated-test-environments-with-seeded-data-for.md · rules/
• acceptance-testing-use-example-mapping-to-discover-acceptance-criteria-rules.md · rules/
• acceptance-testing-use-hooks-before-after-for-setup-and-teardown-not-step.md · rules/
• acceptance-testing-use-parameterized-steps-with-cucumber-expressions-or-regex.md · rules/
• acceptance-testing-use-scenario-outlines-data-tables-for-testing-multiple.md · rules/
• acceptance-testing-write-specifications-before-code.md · rules/
• acceptance-testing-write-specifications-in-domain-language-not-ui.md · rules/

SKILL.md (first lines)

# Acceptance Testing (BDD)

## Overview
Acceptance testing verifies that software meets business requirements by executing human-readable specifications. Behavior-Driven Development (BDD) bridges the gap between business stakeholders and developers through a collaborative workflow: business rules are written as executable specifications (feature files), automated with step definitions, and run as part of the CI pipeline.

> For Gherkin specification syntax (Given/When/Then), see **specs/documentation/gherkin**.
> For Gauge specification syntax (Markdown specs), see **specs/documentation/gauge**.

## BDD Workflow

```
  Collaborate          Specify            Automate           Validate
 ┌──────────┐     ┌──────────────┐    ┌──────────────┐   ┌──────────────┐
 │ Business  │────►│   Feature    │───►│    Step      │──►│  CI Pipeline │
 │ + Dev +   │     │   Files      │    │  Definitions │   │  Execution   │
 │ QA discuss│     │ (Gherkin/    │    │ (code that   │   │  + Reports   │
 │ examples  │     │  Gauge spec) │    │  runs specs) │   │              │
 └──────────┘     └──────────────┘    └──────────────┘   └──────────────┘
```

1. **Collaborate** — Business, dev, and QA discuss requirements using concrete examples (Example Mapping, Three Amigos).
2. **Specify** — Write executable specifications in Gherkin or Gauge Markdown format.
3. **Automate** — Implement step definitions that translate specification steps into code.
4. **Validate** — Run specifications as automated tests in CI; generate living documentation.

---

## Cross-Platform Tools

| Tool | Languages | Spec Format | Strengths |
|------|-----------|-------------|-----------|
| **Cucumber** | Java, JS/TS, Ruby | Gherkin (.feature) | Industry standard, largest ecosystem |
| **SpecFlow / Reqnroll** | C# (.NET) | Gherkin (.feature) | .NET-native, context injection, parallel execution |
| **Behave** | Python | Gherkin (.feature) | Pythonic, fixtures, environment hooks |
| **Gauge** | Java, JS, C#, Python, Ruby, Go | Markdown (.spec) | Markdown specs, concept reuse, data tables |
| **Godog** | Go | Gherkin (.feature) | Go-native, godog.Suite, step definitions |

---

## Gherkin Feature File Example

```gherkin
# features/user-registration.feature
Feature: User Registration
  As a new visitor
  I want to create an account
  So that I can access personalized features

  Background:
    Given the registration page is displayed

  Scenario: Successful registration with valid details
    When I fill in the registration form with:
      | field    | value              |
      | name     | Jane Doe           |
      | email    | jane@example.com   |
      | password | SecurePass123!     |
    And I accept the terms of service
    And I click the "Register" button
    Then I should see a welcome message "Welcome, Jane Doe!"
    And a confirmation email should be sent to "jane@example.com"

  Scenario: Registration fails with duplicate email
    Given a user exists with email "jane@example.com"
    When I fill in the registration form with:
      | field    | value              |
      | name     | Jane Doe           |
      | email    | jane@example.com   |
      | password | SecurePass123!     |
    And I click the "Register" button
    Then I should see an error "An account with this email already exists"

  Scenario Outline: Registration fails with invalid input
    When I fill in "<field>" with "<value>"
    And I click the "Register" button
    Then I should see an error "<error>"

    Examples:
      | field    | value        | error                              |
      | name     |              | Name is required                   |
      | email    | not-an-email | Please enter a valid email address |
      | password | short        | Password must be at least 8 chars  |
```

---

## Step Definitions by Language

### JavaScript / TypeScript (Cucumber.js)

```javascript
// features/step-definitions/registration.steps.js
const { Given, When, Then } = require("@cucumber/cucumber");
const { expect } = require("@playwright/test");

Given("the registration page is displayed", async function () {
    await this.page.goto("/register");
    await expect(this.page.locator("h1")).toHaveText("Create Account");
});

Given("a user exists with email {string}", async function (email) {
    // Seed the database or call an API to create the user
    await this.api.post("/test/seed-user", { email });
});

When("I fill in the registration form with:", async function (dataTable) {
    const rows = dataTable.rowsHash();
    for (const [field, value] of Object.entries(rows)) {
        await this.page.fill(`[name="${field}"]`, value);
    }
});

When("I fill in {string} with {string}", async function (field, value) {
    await this.page.fill(`[name="${field}"]`, value);
});

When("I accept the terms of service", async function () {
    await this.page.check("#terms-checkbox");
});

From onfire7777/universal-ai-skills-library, MIT.

More from onfire7777/universal-ai-skills-library