urchin/tests/Cross-shell testing/.test-run-by-specified-shell/With -s, a sh test should be invoked with sh.

#!/bin/sh

# This script should run with /bin/sh
# regardless of whether -s or -n is passed.

ps -o pid,comm,args | grep $$ | grep /bin/sh
Support for cross-shell testing added, via option `-s <shell>` and env. variable `TEST_SHELL`. * For tests that _source_ shell scripts: option `-s <shell>` now tells urchin to invoke test scripts with the specified shell (only shebang-less and `#!/bin/sh` tests scripts). * For tests that _invoke_ schell scripts: instruct users to write their tests to always invoke via environment variable `TEST_SHELL` (e.g., `$TEST_SHELL ../foo`), and invoke urchin with that variable defined as needed, e.g., `TEST_SHELL=ksh urchin ./tests`; urchin defaults `TEST_SHELL` to `/bin/sh`. See updated `readme.md` for details. 2014-10-17 17:16:12 -04:00			`#!/bin/sh`

update shell cycling logic to match documentation and I updated the documentation already because this new way seems easier to think about 2016-02-29 07:29:47 -05:00			`# This script should run with /bin/sh`
			`# regardless of whether -s or -n is passed.`
Support for cross-shell testing added, via option `-s <shell>` and env. variable `TEST_SHELL`. * For tests that _source_ shell scripts: option `-s <shell>` now tells urchin to invoke test scripts with the specified shell (only shebang-less and `#!/bin/sh` tests scripts). * For tests that _invoke_ schell scripts: instruct users to write their tests to always invoke via environment variable `TEST_SHELL` (e.g., `$TEST_SHELL ../foo`), and invoke urchin with that variable defined as needed, e.g., `TEST_SHELL=ksh urchin ./tests`; urchin defaults `TEST_SHELL` to `/bin/sh`. See updated `readme.md` for details. 2014-10-17 17:16:12 -04:00
support GNU and BusyBox ps 2016-02-29 07:48:13 -05:00			`ps -o pid,comm,args \| grep $$ \| grep /bin/sh`