skills.rest
pyze
pyzeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

bdd-scenarios

Convert specification examples into executable Given/When/Then scenarios using clojure.test.

Updated Mar 16, 2026
Search Tags:#testing#specifications#bdd#clojure#test scenarios#behavior-driven development
One-click install
npx skills add https://github.com/pyze/claude-plugin --skill bdd-scenarios-pyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bdd-scenarios
Source: https://github.com/pyze/claude-plugin/tree/main/skills/bdd-scenarios
Command: npx skills add https://github.com/pyze/claude-plugin --skill bdd-scenarios-pyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill bridges the gap between abstract specifications and concrete, executable tests by converting examples and acceptance criteria into behavior-driven scenarios.

Core Features & Use Cases

  • Specification Conversion: Transforms examples from specification documents into clojure.test scenarios.
  • Behavioral Testing: Focuses on verifying the observable behavior of a system rather than its internal implementation details.
  • Use Case: You have a feature specification with several user stories and acceptance criteria. Use this Skill to automatically generate Given/When/Then test cases for each criterion, ensuring the software behaves as expected.

Quick Start

Convert the provided specification examples into executable clojure.test scenarios.

Frequently Asked Questions about bdd-scenarios

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

FAQPage Schema
How do I convert specification examples into executable clojure.test scenarios?▼

To convert specification examples into executable clojure.test scenarios, you transform acceptance criteria into Given/When/Then test cases. This bridges abstract specifications with concrete test scenarios using clojure.test for behavioral verification.

What is behavior-driven development testing in Clojure?▼

Behavior-driven development testing in Clojure focuses on verifying the observable behavior of a system rather than its internal implementation details. It uses clojure.test to execute Given/When/Then scenarios derived from specification examples.

Can I generate Given/When/Then test scenarios from feature specifications automatically?▼

Yes, you can generate Given/When/Then test scenarios from feature specifications automatically. The process transforms user stories and acceptance criteria into executable clojure.test scenarios, emphasizing behavioral verification over implementation testing.

Does behavior-driven development testing work without external Clojure dependencies?▼

Yes, behavior-driven development scenario generation works without external Clojure dependencies. It converts specification examples directly into clojure.test scenarios, requiring no additional libraries to bridge abstract specs with executable tests.

When should I use behavior-driven scenarios instead of implementation testing in Clojure?▼

Use behavior-driven scenarios instead of implementation testing in Clojure when you want to verify observable system behavior derived from spec examples and uncertainties. This approach bridges abstract specifications with concrete test cases using clojure.test.

Related Skills

Explore More Software Engineering Skills→
AsiaOstrichAsiaOstrich
70

atdd-assistant

Guide Acceptance Test-Driven Development workflows for defining and validating user stories.

Community
Intermediate
maestria-comaestria-co

writing-tests

Plan, write, and run test suites validating code behavior against specifications.

Official
Advanced
saskenubasaskenuba
1

writing-tests

Construct Clojure tests with Fulcro Spec, mocking, spying, and log capture.

Community
Advanced
ssiumhassiumha
9

bdd-practices

Generate Gherkin .feature files from software requirements for BDD workflows.

Community
Advanced