Automated summary
Guidance for writing unit tests for shell scripts with Bats, covering test structures, fixtures, and best practices.
Strengths
- Covers Bats test patterns for exit codes, stdout output, and side effects
- Includes setting up helpers, fixtures, and setup/teardown
- Guides integration of shell tests into CI/CD pipelines
Limitations
- Focused solely on shell scripts, not integration tests beyond shell behavior
- Detailed examples are deferred to an external playbook file not included here
- Explicitly excludes linting and formatting concerns
Reach for this skill when you need to write or structure Bats unit tests for shell scripts or Bash utilities.
Skip it if the project has no shell scripts or if you only need linting or formatting.
Security analysis
SafeThis is a pure documentation/guidance skill describing Bats testing conventions. It declares no tools, contains no executable code, no network calls, no secret handling, and no destructive commands. The only reference is to a local resource file within the skill bundle, so listing it presents no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Write Bats unit tests for our scripts/deploy.sh covering exit codes, log output, and cleanup on failure.Set up a Bats test suite with helpers and fixtures for our CLI tool and wire it into GitHub Actions.Help me do TDD on a new backup.sh utility: write failing Bats tests first, then the implementation.name: bats-testing-patterns description: "Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities." risk: unknown source: community date_added: "2026-02-27"
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.mdfor detailed patterns and examples.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/bats-testing-patterns-mryiqi5a/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/bats-testing-patterns-mryiqi5a' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/bats-testing-patterns-mryiqi5a/download' --output '.skill-downloads/bats-testing-patterns-mryiqi5a/SKILL.md.part' && mv '.skill-downloads/bats-testing-patterns-mryiqi5a/SKILL.md.part' '.skill-downloads/bats-testing-patterns-mryiqi5a/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/bats-testing-patterns-mryiqi5a/SKILL.md' && test -s '.skill-downloads/bats-testing-patterns-mryiqi5a/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/bats-testing-patterns' && cp -R '.skill-downloads/bats-testing-patterns-mryiqi5a' '.claude/skills/bats-testing-patterns'Cursor
test -f '.skill-downloads/bats-testing-patterns-mryiqi5a/SKILL.md' && test -s '.skill-downloads/bats-testing-patterns-mryiqi5a/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/bats-testing-patterns' && cp -R '.skill-downloads/bats-testing-patterns-mryiqi5a' '.cursor/skills/bats-testing-patterns'Codex
test -f '.skill-downloads/bats-testing-patterns-mryiqi5a/SKILL.md' && test -s '.skill-downloads/bats-testing-patterns-mryiqi5a/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/bats-testing-patterns' && cp -R '.skill-downloads/bats-testing-patterns-mryiqi5a' '.agents/skills/bats-testing-patterns'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/bats-testing-patterns-mryiqi5a'openskills read 'bats-testing-patterns-mryiqi5a'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/bats-testing-patterns-mryiqi5a/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.