
Cucumber Gherkin
This is your reference for writing executable specifications in plain English using Cucumber and Gherkin syntax. It covers the full Gherkin keyword set (Feature, Scenario, Given/When/Then, Background, Scenario Outline, Rule), Ruby step definitions with Cucumber Expressions, hooks for setup and teardown, and data tables for parameterized tests. The guide emphasizes declarative scenarios over imperative click-by-click scripts, which keeps your feature files readable by non-technical stakeholders. Use this when implementing BDD in Ruby or Rails projects, writing acceptance tests with Capybara, or when you need to bridge the gap between business requirements and automated testing.
- skills.sh installs
- 215
- GitHub stars
- 12
- last updated
- Aug 21, 2026
Install
$ npx -y skills add el-feo/ai-context --skill cucumber-gherkin --agent claude-codeInstalls into .claude/skills of the current project.
Files
Cucumber & Gherkin
BDD testing framework with plain-text executable specifications and Ruby step definitions.
Feature file (.feature) ──> Step Definitions (Ruby) ──> System under test
Gherkin Quick Reference
Feature: Short description
Optional multi-line description.
Background:
Given common setup for all scenarios
Rule: Business rule grouping (Gherkin 6+)
Scenario: Concrete example
Given an initial context
When an action occurs
Then expected outcome
And additional assertion
But negative assertion
Scenario Outline: Parameterized
Given there are <start> items
When I remove <remove> items
Then I should have <remaining> items
Examples:
| start | remove | remaining |
| 12 | 5 | 7 |
| 20 | 5 | 15 |
Step keywords: Given (setup), When (action), Then (assertion), And/But (continuation), * (bullet)
Data tables:
Given the following users exist:
| name | email | role |
| Alice | alice@example.com | admin |
Sponsors
Details
- Repository
- github.com/el-feo/ai-context
- Categories
- Frontend Development, Testing & QA, Documentation, AI & Agent Building
- First seen
- Jun 3, 2026