4 ms·
Since the project I work on (https://spdk.io https://spdk.io) largely produces a set of executables as output, it was most natural to write the tests in bash. T
by benlwalker 6y ago
Since the project I work on (https://spdk.io https://spdk.io) largely produces a set of executables as output, it was most natural to write the tests in bash. There's one top level bash script that kicks off the full suite of tests and thousands and thousands of lines of tests all written as bash scripts stringing together calls to these executables.
One of these tests is to run shellcheck against all of the scripts in the repo. We don't allow any modifications to scripts without shellcheck giving them the green light now. The quality of our tests has increased dramatically since this was instituted - it's a really great tool.
- afrodc_ 6y agoCan you expand on why y'all thought Bash was a natural fit to kick off all your tests?
- zimmund 6y agoAnd talking about tests... I recommend [bats](https://github.com/bats-core/bats-core https://github.com/bats-core/bats-core) for testing! I'm slowly adding tests to my dotfiles using this.