Settings and variable tables: Three dots are handled correctly

[GoogleCodeExporter]

Hi,
i used a three dot notation for an empty ipv4 notation.
It is convert by framework as an empty string.
Do not found this feature in documentation, so i open an issue if not expected.
Thanks

1)test case table
foo.txt
*** Variables ***
${bar}            ...

*** Test Cases ***
spam
    Log Variables

2) exec test
$pybot foo.txt

3) In report ${bar} is empty

$ pybot --version
Robot Framework 2.7.7 (Python 2.6.6 on linux2)
$ cat /etc/issue
Debian GNU/Linux 6.0 \n \l

Original issue reported on code.google.com by granu...@gmail.com on 1 Mar 2013 at 1:45

[GoogleCodeExporter]

This is a bug related to how continued rows are handled. What actually happens 
here is that those three dots are ignored and as a result you got a value that 
is just an empty string. I was able to get the problem fixed but I still want 
to test does using ellipsis like this cause problems elsewhere too.

Luckily there are several workarounds for this problem:

1) Escape the three does with a backslash:

*** Variables ***
${bar}            \...

2) Set the value as suite variable, for example, in suite setup:

*** Settings ***
Suite Setup        Set Suite Variable    ${bar}    ...

3) Create the variable in a variable file.

Because there are workarounds, this issue isn't severe enough to require new 
2.7 minor release. If 2.7.8 is released for other reasons, this definitely 
should be included, though, and it will latest be fixed in 2.8.

Original comment by pekka.klarck on 5 Mar 2013 at 8:30

• Changed state: Accepted
• Added labels: Target-2.7.8

[GoogleCodeExporter]

Original comment by jussi.ao...@gmail.com on 6 Mar 2013 at 1:56

• Added labels: Target-2.8, alpha1
• Removed labels: Target-2.7.8

[GoogleCodeExporter]

Original comment by jussi.ao...@gmail.com on 6 Mar 2013 at 2:04

• Changed title: Variable with three dot are interpreted as empty variable

[GoogleCodeExporter]

Original comment by tatu.ka...@eficode.com on 26 Mar 2013 at 2:42

• Changed state: Started

[GoogleCodeExporter]

This issue was closed by revision e115b037625f.

Original comment by tatu.ka...@eficode.com on 27 Mar 2013 at 1:05

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by tatu.ka...@eficode.com on 27 Mar 2013 at 1:12

• Changed state: Done

[GoogleCodeExporter]

Needs to check if documentation need updating

Original comment by tatu.ka...@eficode.com on 2 Apr 2013 at 11:23

• Changed state: Review

[GoogleCodeExporter]

No need to update documentation

Original comment by tatu.ka...@eficode.com on 19 Apr 2013 at 2:02

[GoogleCodeExporter]

It took me some time to understand why the problem actually occurred. After I 
understood it, I realized that the same problem occurs also with most settings. 
Updating summary accordingly.

Original comment by robotframework@gmail.com on 7 May 2013 at 2:13

• Changed title: Three dots as value is not handled correctly in variable table and with some settings
• Changed state: Done

[GoogleCodeExporter]

This issue was updated by revision 8cab924ff09c.

Moved the fix from VariablePopulator to _PropertyPopulator to get it also to
SettingPopulator. Also used a different, and hopefully a bit more clear,
solution to fix the problem. Using a flag is always a bit ugly, but in this
case it helps understanding the intention of the code.

Also added tests for handling ... in settings table.

Original comment by robotframework@gmail.com on 7 May 2013 at 2:21

[GoogleCodeExporter]

Original comment by anssi.sy...@eficode.com on 31 May 2013 at 12:48

• Changed title: Settings and variable tables: Three dots are handled correctly

[GoogleCodeExporter]

Original comment by tatu.ka...@eficode.com on 31 May 2013 at 1:54

• Removed labels: alpha1