You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have a keyword definition with an inline argument in the middle, it will currently always show up in the results. For example:
Enter ${username} into form and click the register button
Currently the keyword completion code picks keywords to suggest using a wildcard matcher that treats inline variables as wildcards. This is done in order to make sure the following keyword call matches the above keyword declaration:
Example testcase
Enter kalle into form and click the register button
It can also be the other way around, where the keyword call uses a variable, while the keyword definition does not. Or even a combination of the two.
The extra matches occur because I was experimenting with substring matches and the code is not finished yet. In a typical scenario the user might not remember the exact keyword name and enter for example just "register" hoping to get a list of keywords containing "register". So my quick hack was to put some dummy variables around the search string to get a substring search. But it didn't work out so well.
Need to rewrite the matching logic a little bit
The text was updated successfully, but these errors were encountered: