urchin -sh to urchin -x
This commit is contained in:
parent
5e06ffb1c1
commit
b0429315ec
4
HISTORY
4
HISTORY
|
@ -1,7 +1,7 @@
|
|||
HISTORY
|
||||
-------
|
||||
|
||||
Version 0.0.3
|
||||
Version 0.0.4
|
||||
---------------------
|
||||
General tidying
|
||||
|
||||
|
@ -9,7 +9,7 @@ Run with different shells in three ways
|
|||
|
||||
* urchin -s
|
||||
* $TEST_SHELL variable with $TEST_SHELL
|
||||
* $TEST_SHELL variable with urchin -sh
|
||||
* $TEST_SHELL variable with urchin -x
|
||||
|
||||
Before version 0.0.3
|
||||
----------------------
|
||||
|
|
|
@ -138,13 +138,13 @@ To test with multiple shells in sequence, use something like:
|
|||
urchin -s $shell ./tests
|
||||
done
|
||||
|
||||
#### (c) Cross shell tests with `urchin -sh` (experimental)
|
||||
#### (c) Cross shell tests with `urchin -x` (experimental)
|
||||
If you run urchin with the `-sh` flag, it will be as if you ran
|
||||
`$TEST_SHELL`. Unless `$TEST_SHELL` isn't set, in which case it'll
|
||||
be as if you ran `/bin/sh`. Putting this in she shebang line might
|
||||
eventually work out to be a cleaner way of doing cross-shell testing.
|
||||
|
||||
#!/usr/bin/env urchin -sh
|
||||
#!/usr/bin/env urchin -x
|
||||
test a = a
|
||||
|
||||
## Alternatives to Urchin
|
||||
|
|
Loading…
Reference in New Issue