mcpField
B
bats-testing-patterns

bats-testing-patterns

github.com/sickn33Testing & quality48.8k195 installsUpdated today
Repository

About bats-testing-patterns

A guidance skill for testing shell scripts with Bats. It covers test structure, fixtures, edge cases, setup and teardown, and CI execution for developers validating shell behavior.

Key features

  1. 01Bats unit test patterns
  2. 02Test helpers and fixtures
  3. 03Exit code and output checks
  4. 04Setup and teardown guidance
  5. 05CI testing practices

Use cases

  1. 01Writing shell script unit tests
  2. 02Applying TDD to scripts
  3. 03Testing error cases and side effects
  4. 04Adding shell tests to CI

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill bats-testing-patterns

After installing, type/bats-testing-patternsin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project 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.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported