One-click install
npx skills add https://github.com/grimlor/universal-dev-skills --skill bdd-testing-grimlor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bdd-testing
Source: https://github.com/grimlor/universal-dev-skills/tree/main/skills/bdd-testing
Command: npx skills add https://github.com/grimlor/universal-dev-skills --skill bdd-testing-grimlor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

bdd-testing removes ambiguity and weak test design by enforcing repository-wide BDD conventions, strict mock-boundary rules, diagnostic assertions, and a hard 100% coverage requirement with a remediation workflow.

Core Features & Use Cases

  • BDD conventions for correct system specification: Tests specify system behavior (not units), require a three-part contract (Given/When/Then in docstring and structured body comments), and restrict mocking to the I/O boundary so assertions remain meaningful.
  • Coverage as a blocking requirement: Coverage checks are treated as correctness enforcement, requiring remediation whenever coverage drops below 100%, without allowing “pre-existing gaps.”
  • Failure-mode completeness: Tests must include mandatory defensive guard specs and error-path assertions that validate exception types and meaningful messages.

Quick Start

Use the bdd-testing skill when creating or updating any test class (and when running or auditing coverage) so every requirement in your WHAT clauses is backed by an implemented test and every line must be justified by a real spec.

Frequently Asked Questions about bdd-testing

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

FAQPage Schema
How do I enforce BDD test conventions across multiple programming languages?

BDD test conventions are enforced by validating a strict three-part Given/When/Then contract in both docstrings and structured body comments, ensuring tests specify observable system behavior rather than internal units across multiple languages.

What does strict I/O boundary mocking mean for spec-first development?

Strict I/O boundary mocking restricts mocks to system inputs and outputs so that assertions validate real behavior, preventing meaningless unit tests and ensuring spec-first development accurately reflects system requirements.

How do I stop coverage checks from passing with pre-existing gaps?

Coverage checks stop passing with pre-existing gaps by applying an absolute 100% coverage pass condition that requires immediate remediation for any uncovered lines, treating coverage as a blocking correctness requirement.

How do I write error-path specs that validate exception types and messages?

Error-path specs are written with mandatory defensive guard specifications and diagnostic assertions that validate specific exception types and meaningful error messages, ensuring complete failure-mode completeness in your test suite.

When should I audit test coverage remediation for BDD contracts?

Test coverage remediation should be audited whenever writing, modifying, or reviewing tests to verify every Given/When/Then contract requirement is backed by an implemented test and every line is justified by a real spec.