Testing log message with trailing whitespace is not possible
Issue #3
resolved
Noticed this when converting Python remote server tests to use new StatusChecker. There is a test that verifies that a keyword returns an empty string, and the return value is tested like LOG 3:2 INFO \${ret} = ${EMPTY}
. This used to work with the old statuschecker.py distributed with Robot Framework.
Comments (2)
-
reporter -
reporter - changed status to resolved
Ignore trailing and leading whitespace in log messages.
Fixes
#3. This still needs to be documented.→ <<cset 0fdd6af4a9e0>>
- Log in to comment
Apparently this still worked with 1.0 version also with the new StatusChecker.