Tree @doctests-to-unit-tests (Download .tar.gz)
- ..
- cat.py
- crlf.py
- echo.py
- eg.silly-interpreter
- fail.py
- silly-interpreter.py
- test-appliances-a.markdown
- test-appliances-b.markdown
- test-appliances.expected
- test-bad-indentation.expected
- test-bad-indentation.markdown
- test-crlf.expected
- test-crlf.markdown
- test-err-no-stderr.expected
- test-err-no-stderr.markdown
- test-freestyle-format.expected
- test-freestyle-format.markdown
- test-ill-formed.expected
- test-ill-formed.markdown
- test-implementations-global-a.markdown
- test-implementations-global-b.markdown
- test-implementations-global.expected
- test-input-sections.expected
- test-input-sections.markdown
- test-no-functionality-leak-a.markdown
- test-no-functionality-leak-b.markdown
- test-no-functionality-leak.expected
- test-no-functionality.expected
- test-no-functionality.markdown
- test-no-test-body.expected
- test-no-test-body.markdown
- test-no-tests.expected
- test-no-tests.markdown
- test-pass-fail.expected
- test-pass-fail.markdown
- test-shared-body.expected
- test-shared-body.markdown
- test-stdout-stderr.expected
- test-stdout-stderr.markdown
- test-substring-error.expected
- test-substring-error.markdown
- test-utf8.expected
- test-utf8.markdown
- test-var-subst-no-eol.expected
- test-var-subst-no-eol.markdown
test-err-no-stderr.markdown @doctests-to-unit-tests — 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-body-text)' '' 1"
-> Tests for functionality "Error on stdout"
| this is the error message
? this is the error message