Would it be possible to add "trim" parameter to keyword "Should Be Equal As Strings" (+related keywords)?
Many times I need to compare two strings, but there are some trailing or leading whitespaces in the actual value, which I don't care about, so I always have to trim them before. Having trim as a parameter in these keywords would help me a lot :)

Feature requests

It would extend to keyword Wait Until Page Contains allow to add option Limit that works the same as in keywords Page Should Contain Element.

Currently to use this feature its require to use WUKS with this keyword
|Wait Until Keyword Succeeds | ${Timeout} | ${iteration} | Page Should Contain Element | ${locator} | limit=4|

Its less clear code then
| Wait Until Page C

Allure report doesn't contain parameters from Scenario Outline

Feature: Some Feature
Scenario: Some Scenario
Given variable is <a_value>
When we add <b_value>
Then the result will be <c_value>

Examples:
| a_value | b_value | c_value |
| 2 | 3 | 5 |
| 3 | 3 | 6 |

The data from "Exambles" doesn't pass to allure repor

Swipe by direction is still not implemented, yet the documentation has this function already. Can this be removed or updated somehow?

The opencv capture should not trigger a resize of the swing gui. Instead we should have the VideoWidget handle auto resizing so the swing gui doesn't get so large it goes off the screen.

From https://asyrjasalo.github.io/RESTinstance/#Array I wasn't sure how to use enum and validations. Would be wonderful to have more examples,and maybe something comples like constraints over an array of objects. Thanks.

I had to install geckodriver in order to pass the test. It took me a while to figure that out. Being that this tutorial is for new users, that might be a helpful note to put in the readme.

( Possibly same as issue #5 )

( From https://groups.google.com/forum/#!topic/robotframework-users/017w6G7HljE%5B1-25%5D )

If you include some regexp code, it breaks highlighting after the regexp is defined. The following code will show this issue.

*** Settings ***
Documentation           Verify ability to upgrade and downgrade FW
Suite Setup             yada yada yada   ${VAR_1}   

We need to provide more information for users first landing on the repository. Right now we just rely on user knowledge, the docs, and the example tests. However for a library aimed at helping not only existing teams, but new teams get set up we need a more comprehensive guide to importing and using the libraries.

If an element is not present in JSON I would expect Get Value From Json keyword to fail instead of returning an empty list.

How do you think about it?

Cheers
Tset 🤖

• Add who and how (Issue) needs to be contacted at the zofar-team
  • add a template for what zofar needs (dzhw/zofar#333 (comment))
• add, that and why we use pages and why (not) questions
  • atm (still? ask Christian) questions are not the questions we need but a technical dimension that we can't work with
  • "by default" zofar links the