add-assertion

Create Bash assertion functions in bashunit using TDD cycles.

421|52|Updated Sep 4, 2023
One-click install
npx skills add https://github.com/TypedDevs/bashunit --skill add-assertion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-assertion
Source: https://github.com/TypedDevs/bashunit/tree/main/.claude/skills/add-assertion
Command: npx skills add https://github.com/TypedDevs/bashunit --skill add-assertion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured workflow to add new assertion functions to bashunit using a disciplined TDD process, ensuring test-driven development is consistently followed.

Core Features & Use Cases

  • Planning and drafting a new assertion task file with acceptance criteria.
  • Studying existing assertion patterns and integrating with the framework.
  • Executing RED-GREEN-REFACTOR cycles, documenting changes, and updating docs.

Quick Start

Initiate a new add-assertion task by drafting a task file, studying existing assertion patterns, and implementing a minimal RED-GREEN-REFACTOR cycle.

Frequently Asked Questions about add-assertion

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

FAQPage Schema
How do I add new custom assertions to bashunit using TDD?

To add bashunit assertions using TDD, draft a task file with acceptance criteria, study existing assertion patterns, execute RED-GREEN-REFACTOR cycles, export the new function, and update supporting documentation.

What is the workflow for creating Bash test assertions with test-driven development?

The TDD workflow for creating Bash test assertions involves planning scope, pattern-matching existing styles, coding minimal tests, and integrating the new assertion function into the framework with required documentation updates.

Do I need to create a task file before writing a new bashunit assertion?

Yes, task-file creation is required before writing a new bashunit assertion to define scope, establish acceptance criteria, and document the planned integration steps for the testing workflow.

How do I match existing assertion patterns when adding a test function in Bash?

To match existing assertion patterns when adding a Bash test function, study the bashunit framework's current assertion styles to ensure your new function integrates consistently before starting the RED-GREEN-REFACTOR cycle.

What steps are required to integrate a new assertion function into a Bash testing framework?

Integrating a new assertion function into a Bash testing framework requires exporting the new function, verifying it passes the RED-GREEN-REFACTOR test cycles, and updating all supporting framework documentation.

When should I not use a TDD-driven approach to add Bash assertions?

You should avoid a TDD-driven approach for Bash assertions if your task lacks defined acceptance criteria or falls outside the scope of pattern-matching existing framework styles, as task-file creation and structured planning are required.