shunit2
shellcheck-repl
| shunit2 | shellcheck-repl | |
|---|---|---|
| 4 | 4 | |
| 1,549 | 15 | |
| - | - | |
| 3.5 | 3.1 | |
| 3 months ago | 4 months ago | |
| Shell | Shell | |
| Apache License 2.0 | ISC License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
shunit2
-
Pure Bash Bible
> or something that would proper unit testing
<https://github.com/kward/shunit2>
-
First time writing bash scripts for work, not sure if this is true elsewhere
https://github.com/kward/shunit2 is your friend here.
-
AWK an old-school tool today
And in case you are thinking how powerful this is and like me trying to take it further to create small AWK powered "apps" to do the monotonous tasks while wondering how can you verify if what you are coding is valid, you can execute any number of unit tests for shell scripts, and therefore, AWK scripts using shunit2
-
ShellCheck: A static analysis tool for shell scripts
Alongside ShellCheck, I also use shUnit2 as my unit testing framework. Yes, you should test your bash.
https://github.com/kward/shunit2
shellcheck-repl
-
Shell Script Best Practices, from a decade of scripting things
> "Use shellcheck."
(Disclaimer: I'm one of the authors)
After falling in love with ShellCheck several years ago, with the help of another person, I made the ShellCheck REPL tool for Bash:
https://github.com/HenrikBengtsson/shellcheck-repl> -
Bash Pitfalls
Thank you, and thanks for the suggestion. Yes, it should be possible to keep the SC2154 check. I probably just disabled it as a quick fix when first started out. I'm tracking this in https://github.com/HenrikBengtsson/shellcheck-repl/issues/15.
> You'd also want to take into account special variables like $RANDOM and $HOSTNAME, but that's pretty trivial.
It seems like ShellCheck is already aware of these special Bash variable, e.g. 'echo $RANDOM' will not trigger SC2154 (or even SC2086 that otherwise asks you to quote variables).
-
ShellCheck: A static analysis tool for shell scripts
shellcheck-repl: Validation of Shell Commands Before Evaluation
https://github.com/HenrikBengtsson/shellcheck-repl
This tool validates your commands at the Bash prompt using ShellCheck and refuses to evaluate them if there's a mistake. It ignores a set of rules that doesn't play well with oneliners.
(Disclaimer: I'm one of the authors)
What are some alternatives?
bats-core - Bash Automated Testing System
shellharden - The corrective bash syntax highlighter
shellspec - A full-featured BDD unit testing framework for bash, ksh, zsh, dash and all POSIX shells
ShellCheck - ShellCheck, a static analysis tool for shell scripts
pure-bash-bible - 📖 A collection of pure bash alternatives to external processes.
sh - A shell parser, formatter, and interpreter with bash support; includes shfmt
isort - A Python utility / library to sort imports.
etc - Things that are too small to keep in a separate repo, but too important not to version them.
dmenu-scripts - Serious fun with dmenu