Tree @rel_0_9_2014_0525 (Download .tar.gz)
- ..
- cat.py
- crlf.py
- echo.py
- eg.silly-interpreter
- fail.py
- silly-interpreter.py
- test-crlf.expected
- test-crlf.markdown
- test-err-no-stderr.expected
- test-err-no-stderr.markdown
- test-no-tests.expected
- test-no-tests.markdown
- test-substring-error.expected
- test-substring-error.markdown
- test-utf8.expected
- test-utf8.markdown
- test1.expected
- test1.markdown
- test10.expected
- test10.markdown
- test11.expected
- test11.markdown
- test2.expected
- test2.markdown
- test3.expected
- test3.markdown
- test4.expected
- test4.markdown
- test5.expected
- test5.markdown
- test6.expected
- test6a.markdown
- test6b.markdown
- test7.expected
- test7a.markdown
- test7b.markdown
- test8.expected
- test8a.markdown
- test8b.markdown
- test9.expected
- test9.markdown
test-err-no-stderr.markdown @rel_0_9_2014_0525 — view markup · raw · history · blame
Falderal Test: err-no-stderr
When running a failing test, if the implementation finished with a failing
exit code, but did not provide anything on stderr, expect the error message
to be on stdout.
-> Functionality "Error on stdout" is implemented by shell command
-> "python fail.py '%(test-text)' '' 1"
-> Tests for functionality "Error on stdout"
| this is the error message
? this is the error message