You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In pipe-separated files, if I have a single pipe in a Settings table I get the error "Non-existing setting '|'". I think instead, robot should just ignore the line.
Run this test suite to get the error:
*** Settings ***
| Suite Setup | Log | In suite setup...
|
*** Test Cases ***
| Hello
| | log | hello, world
I would like to be able to have (mostly-)blank lines in settings tables, but robot throws the error "Non-existing setting '|'
The error goes away if I leave the line completely blank, but I would like to have the option of keeping the vertical pipe there, because I think it makes the test easier to read. In this contrived example it doesn't really matter, but in real world tests I like to separate my libraries and resource files from other settings, and the vertical bar makes it all visually appear as a single table rather than two tables separated by a blank line, eg:
pekkaklarck
changed the title
erroneous error "Non-existing setting '|'" in pipe-delimited file
In plaint text files | alone should be considered empty line in pipe-separated format
Oct 6, 2014
In pipe-separated files, if I have a single pipe in a Settings table I get the error "Non-existing setting '|'". I think instead, robot should just ignore the line.
Run this test suite to get the error:
I would like to be able to have (mostly-)blank lines in settings tables, but robot throws the error "Non-existing setting '|'
The error goes away if I leave the line completely blank, but I would like to have the option of keeping the vertical pipe there, because I think it makes the test easier to read. In this contrived example it doesn't really matter, but in real world tests I like to separate my libraries and resource files from other settings, and the vertical bar makes it all visually appear as a single table rather than two tables separated by a blank line, eg:
The text was updated successfully, but these errors were encountered: