Skill

test-scripts-and-infrastructure

Structures shell test scripts for infrastructure like Docker, Docker Compose, and Kubernetes. Enforces behavioral tests via execution, cleanup scripts, and end-to-end CI workflows.

Docker

Docker Compose

npx claudepluginhub humansintheloop-dev/humansintheloop-dev-workflow-and-tools --plugin idea-to-code

Tool Access

This skill uses the workspace's default tool permissions.

Preview

IMPORTANT:

SKILL.md

Similar Skills

bats-testing-patterns

36.4k

Guides unit testing shell scripts with Bats including test patterns, fixtures, best practices, TDD, CI/CD setup, and edge case handling.

1 file

antigravity-awesome-skills

bats-testing-patterns

682

Guides Bats patterns for unit testing shell scripts, covering fixtures, exit codes, output, side effects, TDD, edge cases, and CI/CD setup.

1 file

rmyndharis-antigravity-skills

bash-testing

Guides bash/shell script testing using shunit2 (xUnit-style) and shellspec (BDD-style) frameworks. Covers installation, assertions, test structures, setup/teardown, and function isolation.

1 file

bash-development

Stats

Parent Repo Stars21

Parent Repo Forks1

Last CommitMar 18, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

When writing tests for shell scripts or infrastructure:

Tests MUST execute the script and verify the observable outcome

Tests MUST NOT use grep/static analysis to check file contents

Tests MUST NOT check for file existence as a proxy for correctness

Before writing a test, state: "The observable outcome is: [X]"

If a test can pass without running the code, it's not a behavioral test

ALWAYS put the test scripts in a test-scripts/ subdirectory

If necessary, create a test-scripts/test-cleanup.sh script that cleans up test state, e.g. removes docker containers

Write test-xyz.sh scripts for specific behaviors, e.g. test-init-ca.sh tests init-ca.sh

ALWAYS Incrementally create a test-end-to-end.sh script that first runs test-cleanup.sh and then runs each test-xyz.sh script in sequence

CI workflows should call ./test-scripts/test-end-to-end.sh, not individual test scripts

When adding new test scripts, add them to test-end-to-end.sh rather than modifying CI configuration

IMPORTANT:

NEVER WRITE SHELL scripts that directly test Java applications ** Java applications should ALWAYS be directly tested using JUnit Tests executed by Gradle. ** NEVER write shells script that use gradlew bootrun. ** NEVER write shell scripts like this: test-scripts/test-health.sh that starts the application, waits for startup, curls /actuator/health, and asserts HTTP 200 with status UP

Shell scripts are for testing infrastructure such a docker, docker compose, kubernetes etc.

When writing tests for shell scripts or infrastructure:

Tests MUST execute the script and verify the observable outcome
Tests MUST NOT use grep/static analysis to check file contents
Tests MUST NOT check for file existence as a proxy for correctness
Before writing a test, state: "The observable outcome is: [X]"
If a test can pass without running the code, it's not a behavioral test
ALWAYS put the test scripts in a test-scripts/ subdirectory
If necessary, create a test-scripts/test-cleanup.sh script that cleans up test state, e.g. removes docker containers
Write test-xyz.sh scripts for specific behaviors, e.g. test-init-ca.sh tests init-ca.sh
ALWAYS Incrementally create a test-end-to-end.sh script that first runs test-cleanup.sh and then runs each test-xyz.sh script in sequence
CI workflows should call ./test-scripts/test-end-to-end.sh, not individual test scripts
When adding new test scripts, add them to test-end-to-end.sh rather than modifying CI configuration