urchin/tests/Cross-shell testing/Environment variable TEST_SHELL should default to sh if empty.

#!/bin/sh

# Tests support for either passing through or defining a default value for environment variable TEST_SHELL.
# (for test scripts that want to invoke shell scripts with a specified shell).

# Test if $TEST_SHELL - if *defined, but empty* - is exported with value '/bin/sh' by urchin
# and thus has that value inside the scripts.
TEST_SHELL= $TEST_SHELL \
  ../../urchin ./.test-TEST_SHELL-undefined_or_empty
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 21:16:12 +00:00			`#!/bin/sh`

			`# Tests support for either passing through or defining a default value for environment variable TEST_SHELL.`
			`# (for test scripts that want to invoke shell scripts with a specified shell).`

			`# Test if $TEST_SHELL - if defined, but empty - is exported with value '/bin/sh' by urchin`
			`# and thus has that value inside the scripts.`
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 12:29:47 +00:00			`TEST_SHELL= $TEST_SHELL \`
start moving cross-shell testing tests and also make them more cross-shell test style 2016-02-28 22:23:45 +00:00			`../../urchin ./.test-TEST_SHELL-undefined_or_empty`