Pekka Klärck

PR #3869 is a good start. There is, however, so much work still to be done both internally to handle custom statuses and in log report to show them nicely...

I just rechecked PR #3869 and noticed that there's even more work, including big design decisions, to be made for this to be reasonable enhancement in RF 5.0. In fact,...

This feature isn't currently targeted for any planned release. If someone is interested to look at developing it, I'd be happy to help. Paying for the development is possible as...

We could easily add configuration options controlling the failure message to individual keywords like `Fail`, but it's impossible to add such configuration to all keywords. I guess we could consider...

A problem with `${RANDOM}` is that different users would likely want to have different random values. In some usages a random UUID would be fine, but in others you'd needed...

Pabot solves a totally different problem than the one described here. Pabot runs *tests* (or actually test suites) in parallel, but this issue is about running keywords inside one test...

No updates. Getting this implemented will require a lot of internal changes and it's unlikely they will happen in the near future. At the moment the only way to run...

I agree creating local variables using a hard coded value is a bit annoying and coming up with something nice than ${var} = Set Variable value would be nice. ---...

This won't be in RF 4.0 but let's see could it be added in RF 4.1. Still time to think about the syntax as well.

Too big change for a small release like RF 4.1. Moving to RF 5.0.