Pekka Klärck

This is a real problem, but hard to solve without breaking backwards compatibility massively. The main problem is that `=` is a pretty commonly used in normal arguments. If we'd...

This sounds pretty strange because we let `docutils` handle all reST parsing. Do you possibly use this headings with different keywords? In that case I believe they are parsed in...

Why don't you have separate tests for each iteration?

I still don't understand why you don't have each iteration as a separate test. That basically would mean that instead of using ```robotframework *** Test Cases *** Example [Template] Template...

I see. When using FOR loops with templates you obviously cannot have separate tests like I proposed and splitting should be done somehow by Robot. Splitting probably wouldn't be too...

Resource keyword is a good name otherwise, but it doesn't really work when referring to keywords created in suite files directly. In documentation we could use a different name for...

The problem I have with "user keywords" is that users can create libraries. In general I'd like to lower the barrier between just using the framework and extending it with...

Because our active native English speaking users prefer the User Keyword term, it's clear there would be no benefits with the terminology change. The change would, however, require a lot...

There was long discussion on Slack about this but no clear consensus on what to do. The status quo is keep using the user keyword team and I believe we...

The reason for the error is that suite execution hasn't properly started yet and there is no `` element in the output.xml file under which the `` element belongs to....