aa9044cc97
This is motivated by Google's shell coding standards and will reduce the odds of a naming conflict with other functions (which, of course, would cause terribly odd and difficult-to-find bugs, in both our system and others'). If this seems like it creates long, overly-verbose function names with no relief in sight---you're right. I'll have a solution for that in a bit, as a separate project. ...as a part of my never-ending, growing heap of projects. |
||
---|---|---|
bin | ||
src | ||
test | ||
.gitignore | ||
COPYING | ||
Makefile.am | ||
README.md | ||
configure.ac |
README.md
shspec
#!/bin/bash
describe shspec
it is a BDD framework for shell
expect current-shell-support
to output "bash"
expect pronounciation
to succeed
and to output "shell spec"
end
it is currently under development
expect is-stable
to succeed
and to output "Because of self-testing"
expect is-comprehensive
to fail
and to output "You should check back later."
end
end
License
shspec is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.