Bats isn't a port of anything, and sometimes Bash is the right tool for the job.
I maintain two other projects written in Bash (rbenv and ruby-build). I looked, and couldn't find any suitable testing tools for Bash, so I created Bats.
My criteria for deciding what to work on in the open-source world is: do I need something that doesn't yet exist, or something whose existing implementations are unsuitable? If yes, I try to fill the void as best I can, and package it up nicely so others can use it too.
Comments
Bats isn't a port of anything, and sometimes Bash is the right tool for the job.
I maintain two other projects written in Bash (rbenv and ruby-build). I looked, and couldn't find any suitable testing tools for Bash, so I created Bats.
My criteria for deciding what to work on in the open-source world is: do I need something that doesn't yet exist, or something whose existing implementations are unsuitable? If yes, I try to fill the void as best I can, and package it up nicely so others can use it too.
FWIW here's a vaguely doctest-like tool I wrote: https://github.com/darius/tush
May be unsuitable for you, as you say -- it looks like it takes less typing/punctuation to write the example tests, though.
Wow, I really like the literate style. Great stuff.
Thanks!
Another test framework written in (pure) shell is Sharness: http://git.io/sharness
It was derived from the Git test harness. I'm already using it for a couple of my projects.