bats-testing-patterns

Create a .bats file with @test blocks, use the run command to execute your script, then assert on $status for exit codes and $output for stdout. Add setup and teardown functions to manage temporary directories and fixtures.

Create executable stub scripts in a temporary directory and prepend it to PATH so your stubs shadow real commands like curl. Alternatively, define shell functions with the same name and export them to override external tools.

Yes, Bats produces TAP-compliant output that CI systems understand. Install it via npm or from source in your workflow, then run bats tests/*.bats, optionally with --tap or --parallel flags for reporting and speed.

Yes, you can write tests that invoke your script explicitly with bash, sh, or dash to verify portability. Use the skip command when a shell like dash is not installed on the test machine.

The $output variable joins lines with newlines, which can cause quoting mismatches. Use the $lines array instead to assert on individual lines, such as checking that ${lines[0]} equals the expected first line.