Skill

bats-testing-patterns

Provides Bats patterns and fixtures for unit testing shell scripts, including TDD, CI/CD setup, edge cases, and multi-shell validation.

Bash

CI/CD

testing

devops

From antigravity-awesome-skills

Install

Run in your terminal

npx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-awesome-skills

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

resources/implementation-playbook.md

Skill Content

Similar Skills

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

139.9k

agent-payment-x402

Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.

everything-claude-code

139.9k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

139.9k

Stats

Parent Repo Stars30787

Parent Repo Forks5140

Last CommitMar 27, 2026

Actions

View Source View Plugin View on GitHub View README

Bats Testing Patterns

Comprehensive guidance for writing comprehensive unit tests for shell scripts using Bats (Bash Automated Testing System), including test patterns, fixtures, and best practices for production-grade shell testing.

Use this skill when

Writing unit tests for shell scripts
Implementing TDD for scripts
Setting up automated testing in CI/CD pipelines
Testing edge cases and error conditions
Validating behavior across shell environments

Do not use this skill when

The project does not use shell scripts
You need integration tests beyond shell behavior
The goal is only linting or formatting

Instructions

Confirm shell dialects and supported environments.
Set up a test structure with helpers and fixtures.
Write tests for exit codes, output, and side effects.
Add setup/teardown and run tests in CI.
If detailed examples are required, open resources/implementation-playbook.md.

Resources

resources/implementation-playbook.md for detailed patterns and examples.