I have a project in production and we have some bash scripts and I would like to test to be more sure that everything works as it should and I have been recommended this library that has a great maintenance and it is very active. What do you think?
A bit odd that someone would take this on when BATS is there already. I had a quick look, seems OK apart from the strange choice of camel-case for the assertions, perhaps they're trying to attract the JS/TS crowd?
The more choice the better I suppose, but I think I'll be sticking to BATS.
Thank you very much for your comment. We are just starting to adapt to the more widespread standards within the bash community. We initially focused on getting a solid MVP and didn't give much thought to the fact that using camelCase might seem strange to more experienced members of the community.
In our latest version, we've migrated all the assertions to be snake_case, and we're now gradually doing the same with the library's internal code.
They repeatedly name a parameter "callable", but call the function themselves inside string interpolation. This only works out how they need when it's the last parameter.
What would be the correct term instead of "callable"? It seems you have quite a bit of experience with bash. Would you like to help us with the library?
https://bashunit.typeddevs.com/ https://github.com/TypedDevs/bashunit