TDD Bash

Even though shell scripting was present in every development team that I have worked in, it was almost never tested. Over time, everyone becomes afraid to change code without tests because it might break. This fear grows proportionally with the importance of the code.

This repository is meant to capture the mechanics and reasoning behind test-driven bash code. It also conveys the process behind evolving a good bash codebase.

How to write good bash code?

1. Understand the bash pitfalls
2. Use shellcheck
3. Emphasise on functional code
4. Discover the simplest concepts
5. Explore their optimal composition
6. Use containers for integration testing
7. Stop when the fun stops