Commit Graph

6 Commits (2ec3f8a01e23faaf8a550c0d62c785a22c47dc11)

Author SHA1 Message Date
Mike Gerwitz aa9044cc97 Began move to shspec::* function naming
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.
2014-06-13 21:34:42 -04:00
Mike Gerwitz a116a4ac72 Environment expectations now permit omitting operator
Export expectations will only succeed/fail based on flag checks, whereas the
declare/set expectations will fail on value.
2014-06-13 21:29:38 -04:00
Mike Gerwitz 9045a3298b Added `exports` expectation 2014-06-13 21:29:38 -04:00
Mike Gerwitz 302977eb74 Refactored environment expectations to support grabbing flags 2014-06-13 21:29:38 -04:00
Mike Gerwitz 331a1161b2 Added `declare` as an alias for `set` expectation 2014-06-13 21:29:38 -04:00
Mike Gerwitz 7597677086 Added env var value expectation 2014-06-13 21:29:34 -04:00