bdd-anti-patterns

Identify and refactor anti-patterns in Gherkin BDD scenarios.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/baphled/dotopencode --skill bdd-anti-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bdd-anti-patterns
Source: https://github.com/baphled/dotopencode/tree/main/skills/bdd-anti-patterns
Command: npx skills add https://github.com/baphled/dotopencode --skill bdd-anti-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and correct common mistakes in Behavior-Driven Development (BDD) scenarios, leading to more stable, maintainable, and business-focused tests.

Core Features & Use Cases

  • Identify Anti-Patterns: Detects fragile tests that focus on UI mechanics or implementation details rather than business behavior.
  • Provide Fixes: Offers concrete examples and strategies to refactor problematic scenarios.
  • Use Case: Refactor brittle end-to-end tests that are failing due to minor UI changes, ensuring they focus on the intended business outcome.

Quick Start

Use the bdd-anti-patterns skill to audit the Gherkin scenario 'When I click the submit button'.

Frequently Asked Questions about bdd-anti-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why are my BDD tests fragile and breaking due to minor UI changes?

BDD tests become fragile when Gherkin scenarios depend on UI mechanics or implementation details rather than business behavior. Refactoring them to test workflow over presentation ensures end-to-end tests remain stable despite minor UI updates.

How do I refactor Gherkin scenarios that depend on implementation details?

Refactoring implementation-dependent Gherkin scenarios involves shifting focus from UI mechanics to business clarity. You rewrite steps to describe intended business outcomes, ensuring the scenario tests behavior over presentation and workflow over mechanics.

What are common BDD anti-patterns in Gherkin end-to-end testing?

Common BDD anti-patterns include Gherkin scenarios lacking business clarity, testing UI mechanics instead of behavior, and creating implementation-dependent steps. Identifying these issues helps rectify fragile tests and ensures end-to-end testing validates actual business outcomes.

Does this approach work for refactoring brittle end-to-end tests?

Yes, this approach specifically targets brittle end-to-end tests by identifying anti-patterns in your Gherkin scenarios. It provides concrete strategies to refactor tests failing from minor UI changes so they validate business outcomes instead of presentation mechanics.

Can I use this to fix tests that lack business clarity in Gherkin?

Yes, you can use this to fix Gherkin scenarios lacking business clarity. It identifies tests focused on implementation details and provides concrete examples to refactor them, ensuring behavior-driven development scenarios express intended business behavior.