shell-testing-framework_skill

Overview

This skill provides expert guidance for building and maintaining bash test suites using unix-goto patterns. It enforces a strict arrange-act-assert structure, four required test categories, and a mandate of 100% coverage for core features. It also includes patterns for assertions, test helpers, and performance measurement.

How this skill works

The skill describes a standard test file layout, helper functions for pass/fail counting, and test execution with clear exit codes. It explains how to write unit, integration, edge case, and performance tests, using the arrange-act-assert pattern for every test function. It also details coverage rules, performance targets, and practical examples for cache, history, bookmarks, and navigation behaviors.

When to use it

• Writing comprehensive test suites for bash shell scripts
• Enforcing 100% test coverage on core features
• Organizing tests into unit, integration, edge case, and performance categories
• Creating repeatable assertion patterns and test helpers
• Adding performance and scale tests to CI pipelines

Best practices

• Always write tests before implementing features (TDD): red → green → refactor
• Follow the exact test file structure: setup, counters, helpers, test functions, execution, summary
• Make every test function follow Arrange-Act-Assert and exit with meaningful codes
• Cover every function and code path; include error and boundary cases to meet 100% coverage
• Keep unit tests fast and isolated; reserve integration and performance tests for CI or separate pipelines
• Use reproducible fixtures and cleanup to avoid flakiness and ensure deterministic results

Example use cases

• Unit test cache lookup behavior for single, multiple, and missing matches
• Integration test navigation flow including cache, history, and bookmarks
• Edge case tests for malformed data, empty files, long paths, special characters, and concurrent access
• Performance tests measuring lookup and build times against targets (<100ms lookup, <5s build)
• Benchmark cache behavior at scale by generating large workspace trees in CI