Development Skill
Angular Migration
Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and…
$15
Bats Testing Patterns
Master Bash Automated Testing System (Bats) for comprehensive shell script testing.
A complete guide to testing shell scripts with Bats (Bash Automated Testing System), the TAP-compliant framework for shell. It teaches isolated, repeatable tests using setup/teardown, the Arrange-Act-Assert structure, command stubbing and mocking, fixture management, and cross-shell portability: so your Bash utilities and CI/CD scripts are validated like real software, not run on hope.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category Development
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
Shell scripts deserve real tests too: isolated, offline and wired into CI. Bats makes that possible, and the skill enforces the discipline around it:
- Scaffolds isolation into every .bats file: setup() creates a mktemp -d work directory, teardown() removes it, and any env var exported inside a test is unset afterwards so nothing leaks between tests.
- Structures each test as Arrange-Act-Assert: fixtures and environment prepared, run my_function captures $status and $output automatically, assertions check exit codes, output strings, the lines array, file existence and permissions.
- Stubs external commands so tests run offline: a stubs directory is prepended to PATH and create_stub writes fake curl, git or sqlite3 scripts with controlled output and exit codes; real network and tools are never touched.
- Tests failure paths as first-class citizens: missing files, empty input, permission denied, invalid options with a usage message, each asserted on both exit code and error output.
- Handles platform portability explicitly: skip when a shell or tool is absent, branches for macOS BSD versus Linux GNU stat syntax, and a CI matrix that runs the suite on both ubuntu and macos.
- Wires it into CI: bats with TAP output runs on every PR, shellcheck sits next to it as the static layer, and a pre-commit hook triggers the Bats tests belonging to any changed .sh file.
One power source. 6 lines out.
bats-testing-patterns · core
core active · 6 lines
- ✓ writing unit tests for s…
Writing unit tests for shell scripts and utilities
- ✓ test-driven development of
Test-driven development of Bash tooling
- ✓ wiring shell tests into
Wiring shell tests into CI/CD pipelines
- ✓ testing error conditions
Testing error conditions and edge cases, not just the happy path
- ✓ mocking external commands
Mocking external commands (curl, git, jq) for network-free tests
- ✓ verifying portability ac…
Verifying portability across bash, sh, and dash
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Each test runs in an isolated temp directory, so order never changes the result
license: perpetual -
Command stubbing decouples unit tests from the network and external dependencies
license: perpetual -
Shift-left testing catches shell regressions on every PR before they reach production
license: perpetual -
TAP output drops straight into GitHub Actions, Makefiles, and parallel runners
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Bats installation and project file-structure conventions
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Engineers maintaining shell scripts who want test-driven confidence and CI coverage for their Bash code.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
Can I test scripts that call curl, aws, or other external commands without actually running them?
Yes: command stubbing and mocking is core here, so you replace those calls with controlled fakes. Your tests stay fast and repeatable instead of hitting real services.
-
Is unit-testing a shell script actually worth it over just running it once?
For a throwaway one-liner, no. For tooling other scripts or pipelines depend on, the setup/teardown and Arrange-Act-Assert structure catches the regressions a single manual run quietly misses.
-
Will these tests confirm my deploy script works against the real environment?
No. Bats verifies units with dependencies stubbed out, not live integration against your actual servers. It proves your logic is correct in isolation; end-to-end validation against real systems is a separate layer.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.