Open dschulten opened 12 years ago
Thanks for the input!
As you pointed out this is fairly experimental plugin. We now have some confidence (based on peoples interest in this plugin) in that it could be a valuable extension to Robot Framework tools. So hopefully we (RF core team) will in future have more time to work on this plugin!
Hi,
I am quite impressed, this plugin has potential. However, it is still experimental.
I am getting a number of syntax errors which seem not to be errors at all, at least RIDE has no problems with them, in part they were entered by RIDE.
Variables setting always says "missing EOFat Variables"
The error message at Variables is "mismatched input '\r\n' expecting RULE_SEPARATOR"
-> No idea what's amiss here
Suite Setup with commented out content
The error message is "mismatched input '\r\n' expecting RULE_SEPARATOR"
Errors on empty Steps
RIDE does not remove settings lines even if you click clear., rather it keeps the step and just removes the content. This leads to the error message "mismatched input '\r\n' expecting RULE_SEPARATOR"
At Force Tags:
At Test Teardown:
Test Teardown without Keyword
Keywords with embedded variables seem not to be supported yet
I have a file with BDD keywords such as:
At Gegeben sei ${keyword}, I get an error: no viable alternative at input '{'
Table Headers for Example Test Cases are not supported
RIDE supports Table Headers for Template Test Cases, as in
The error message says "required (...)+ loop did not match anything at input '" in the * Test cases * line.
Here, ItemNumber and Action are shown as Table Headers in a RIDE template test case. The Space Editor shows a red mark before Item Number. Furthermore, it says "missing EOF at 'No'" on the Test Case name "No Unsupported Contract Actions"
XPath expressions are marked as erroneous
E.g. for @id I get missing '{' at 'id,
What makes things complicated is, that there is not always an xpath= before the locator, as in:
Mail addresses in tests are marked as errors
The message says: missing '{' at 'web.de'
General problem
Non-robot txt files, e.g. within the firefox profile, the libraries folder or the target folder of my project show errors - even the readme.txt in the project root. We might need a project nature or so to handle this, maybe a standard project directory layout which separates test cases and robot resources from libraries and other resources. In general, only source folders should be scanned for errors.