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
7597677086
Added env var value expectation
2014-06-13 21:29:34 -04:00
Mike Gerwitz
683c4cc691
Added `not' expectation
...
Simply negates the result of whatever expectation it is given
2014-05-15 00:45:49 -04:00
Mike Gerwitz
914dafc62a
`match' handler now defined in terms of output abstraction
...
Consequently, now supports `on' clause.
2014-05-13 23:25:27 -04:00
Mike Gerwitz
e4abafa8b4
Converted `be' tests into direct expectation handler test
...
The original implementation was not an expectation handler (for some
reason), so this was an artifact of that approach.
2014-05-13 21:46:00 -04:00
Mike Gerwitz
a59a09007b
Added `silent' expectation handler
2014-05-13 01:25:22 -04:00
Mike Gerwitz
c899f9c170
`output' expectation handler now supports stdout
...
This requires a little bit of file descriptor wizardry, but works; I will
need to abstract it for other handlers that will need to do the same thing.
2014-05-13 01:25:12 -04:00
Mike Gerwitz
89a38a5dc2
Adjusted existing handlers and tests to honor shift argument
...
This will also ensure that the test cases do not break when new arguments
are added, since the existing conventions will remain unchanged.
2014-05-10 00:42:58 -04:00
Mike Gerwitz
c1d1b66fa9
Added `match' expectation
2014-05-09 23:31:47 -04:00
Mike Gerwitz
61ecb6ad82
Added output expectation handler
2014-05-09 02:04:09 -04:00
Mike Gerwitz
6dbf996f3b
Exit code now passed to expectation handlers
2014-05-09 01:13:26 -04:00