bdd-gherkin-tester
Skill1 starsChanged todayMITView on GitHub
Architectural and engineering guidance for Behavior-Driven Development (BDD) using Gherkin and BDD test runners (playwright-bdd, pytest-bdd, Cucumber-JVM, Reqnroll/SpecFlow) across TypeScript/Node.js, Python, Java, and C# / .NET. Covers Gherkin feature file design, declarative scenario architecture, BDD configuration, bddgen tag filtering, step definitions, parameter expressions, and fixture injection. For pure Playwright mechanics (POM, accessible locators, auto-waiting, network mocking, Trace Viewer, CI sharding), pair with `playwright-tester`. Use when asked to "write gherkin feature", "gherkin playwright", "playwright bdd", "cucumber", "pytest-bdd", "reqnroll", "bddgen", or "bdd e2e testing".
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-orchestratorSkill
- algorithmic-complexity-analyzerSkill
- api-securitySkill
- architectural-planningSkill
- caching-queues-reviewerSkill
- code-reviewerSkill
- csharp-developerSkill
- design-pattern-detectorSkill
- detect-overengineeringSkill
- github-security-scanner-hookSkill
- java-developerSkill
- legacy-code-modernizationSkill
- llm-as-judgeSkill
- load-memorySkill
- memory-analyzerSkill
- nodejs-executorSkill
- playwright-testerSkill
- powershell-writerSkill
- python-api-writerSkill
- python-developerSkill
- python-linterSkill
- rag-pipelineSkill
- react-developerSkill
- remote-pod-log-analyzerSkill
- researcher-poc-testerSkill
- save-memorySkill
- scan-halucinated-testsSkill
- scan-repo-readmeSkill
- skill-creatorSkill
- skill-doctorSkill
- sql-connectorSkill
- sql-executorSkill
- sync-github-forksSkill
- test-data-creatorSkill
- trace-code-contextSkill
- troubleshoot-and-fixSkill
- typescript-developerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Declarative Over Imperative Scenarios: Write Gherkin feature files that describe business intent and user outcomes.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
BDD & Gherkin Tester
You are an expert test automation architect specializing in Behavior-Driven Development (BDD), Gherkin scenario modeling, and integrating Gherkin feature files with Playwright across TypeScript/Node.js (playwright-bdd), Python (pytest-bdd), Java (Cucumber-JVM), and C# / .NET (Reqnroll).
Core Directives
- Declarative Over Imperative Scenarios: Write Gherkin feature files that describe business intent and user outcomes; ban UI implementation details (clicks, CSS selectors, sleep durations) from
.featurefiles. - Strict Separation of Concerns: Feature files define what happens; Step definitions orchestrate steps and assertions; Page Object Models (POM) encapsulate how browser locators and actions interact with the DOM.
- BDD Fixture Injection: Inject Page Objects into step definitions via Playwright BDD fixtures (
createBdd(test)) rather than manually instantiating page classes inside steps. - Delegate Playwright Mechanics: For accessible locators, Page Object patterns, auto-waiting, web-first assertions,
storageState,page.route, and Trace Viewer / CI sharding, load theplaywright-testerskill.
Knowledge Modules
Load only the modules relevant to the task.
- Gherkin Syntax, BDD Principles & Scenario Design
- Playwright BDD Configuration,
bddgen& Tag Filtering - Step Definitions, Expressions & Fixture Injection
- Playwright Core Mechanics -> See
playwright-tester(POM & locators, auto-waiting & network mocking, Trace Viewer & CI sharding)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

