Comment #5 on issue 854 by pekka.klarck: Regular expression support for
embedded argument syntax
http://code.google.com/p/robotframework/issues/detail?id=854
1) In the plain text format when a pipe is used a separator we require
spaces around it like `| Example keyword | an argument |`. It would thus be
safe to use it a as a regexp separator in embedded args if no spaces are
allowed.
Although I think it's a good idea not to allow spaces in this use case (a
possible space after the separator should be considered part of the
regexp), I agree that using a pipe could be confusing. Changing the
separator is so easy that we can agree on it even when this feature is
otherwise ready.
2) Have you found the existing acceptance tests for embedded args
functionality? They are in atest/robot/keywords/embedded_arguments.txt and
atest/testdata/keywords/embedded_arguments.txt (I just changed the format
and renamed the file so you need to take an update). To understand how the
acceptance tests are created you should take a look at `atest/README.txt`
and to run them you can use
atest/run_atests.py python atest/robot/keywords/embedded_arguments.txt
3) In addition to the implementation and tests, this also needs to be
documented in the User Guide.
4) How fast you think you can get this done? We try to get RF 2.6 out in
June and getting this in would be nice. You can count on us helping
especially with tests and docs if there's a need.
