The Bash track and I are not getting along right now. I’ve already posted about my problem with the editor. I was trying to edit atbash.sh – maybe, even, that’s why the editor can’t find iteration 2. The test suite seems to claim inability to read it as well. I’ve written code that runs fine on my home system as “bash atbash.sh”, but when I give it to the test suite “bats atbash_cipher.bats” it fails all with this warning appended at the end:
The following warnings were encountered during tests:
bash atbash_cipher.sh encode yesexited with code 127, indicating ‘Command not found’. Use run’s return code checks, e.g.
run -127, to fix this message.
run' in file /usr/local/Cellar/bats-core/1.9.0/lib/bats-core/test_functions.bash, line 297, in test file atbash_cipher.bats, line 10) BW01:run
's commandbash atbash_cipher.sh decode vcvix rhn
exited with code 127, indicating 'Command not found'. Use run's return code checks, e.g.run -127
, to fix this message. (from functionrun’ in file /usr/local/Cellar/bats-core/1.9.0/lib/bats-core/test_functions.bash, line 297,
in test file atbash_cipher.bats, line 68)