shunit2

Good alternatives to bats if you want to write portable test suites that target many shells: - https://github.com/shellspec - https://github.com/kward/shunit2

> or something that would proper unit testing <https://github.com/kward/shunit2>

Alongside ShellCheck, I also use shUnit2 as my unit testing framework. These two combined have let me write some pretty long (~1k loc) bash programs that work. Yes, you should test your bash. https://github.com/kward/shunit2

Shunit2 as well https://github.com/kward/shunit2

Other tips I've found after a year or two of using Bash for many things it shouldn't be used for: - Use shellcheck (static analysis/linter) https://www.shellcheck.net/ - Use shunit2 (unit tests) https://github.com/kward/shunit2 - Use 'local' or 'readonly' to annotate your variables - Trap ctrl+c to gracefully exit (details here https://www.tothenew.com/blog/foolproof-your-bash-script-som...) - Stick to long-form options for readability (--delete over -d for example) - #!/usr/bin/env > #!/bin/bash for portability - Consider setting variable values in a file and importing it at the top of your script to improve refactoring - You will eventually forget how your scripts work - seriously consider if Bash is your best option for anything that needs to last a while!

How might one compare/contast critic.sh against the following? * https://github.com/djui/bashunit * https://github.com/kward/shunit2