shellspec
getoptions
Our great sponsors
| shellspec | getoptions | |
|---|---|---|
| 6 | 7 | |
| 1,017 | 363 | |
| 1.0% | - | |
| 0.0 | 0.0 | |
| about 1 year ago | 5 months ago | |
| Shell | Shell | |
| MIT License | Creative Commons Zero v1.0 Universal |
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.
shellspec
-
[P] Convert Any language to a Linux command (one-liner)
Suggest to look also at ShellSpec
-
Unit test for an installer
I'm thinking to use shellspec to perform the unit testing on Linux boxes, already for the file configuration.
- ShellSpec – A full-featured BDD unit testing framework for dash, bash, ksh, zsh
- ShellSpec: A unit testing framework for shells
-
Bash_unit – bash unit testing framework
If you fancy more BDD-style testing with a Gherkin-like syntax, there is also Shellspec https://shellspec.info / https://github.com/shellspec/shellspec
-
[POSIX] How to Implement --args and How Should Usage Be Formatted
I am developing a testing framework for POSIX compliant shells that has over than 60 options. Since, It is for testing shell scripts, it makes sense to implement it in a shell script, even if it is complex.
getoptions
-
Is there a recommended alternative to getopts?
I like to use https://github.com/ko1nksm/getoptions
- jetopt: a dead simple wrapper around getopt you always dreamed of!
- What is the best way to handle flags?
- Adding options to scripts
-
The easiest way to parse arguments using getoptions for bash and shell scripts
A lot of people have been looking for a best practice to use getopt and getopts for long years. A number of methods to parse arguments were thought up, but no perfect solution was found. However, with the advent of the getoptions, that long journey comes to an end.
-
What is the best practice for handling parameters and flags in a bash script?
Why not use a library instead of implementing it yourself? I wrote getoptions (not getopt or getopts) which many option syntaxes can be easily supported. A lot of options are no longer an obstacle, and there is no need to use another inappropriate language for such a trivial reasons.
- [POSIX] How to Implement --args and How Should Usage Be Formatted
What are some alternatives?
bashcov - Code coverage tool for Bash
argbash - Bash argument parsing code generator
bash-oo-framework - Bash Infinity is a modern standard library / framework / boilerplate for Bash
shflags - shFlags is a port of the Google gflags library for Unix shell.
shunit2 - shUnit2 is a xUnit based unit test framework for Bourne based shell scripts.
kingpin - CONTRIBUTIONS ONLY: A Go (golang) command line and flag parser
Installomator - Installation script to deploy standard software on Macs
jetopt - A friendly wrapper around getopt
bash_unit - bash unit testing enterprise edition framework for professionals
bash-argsparse - An high level argument parsing library for bash
shc - Shell script compiler
bashew - bash script micro-framework - from small stand-alone script to complex projects with CI/CD and testing