-
Notifications
You must be signed in to change notification settings - Fork 767
Provide support for verifying text entered into a textarea element #167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think keep it separate an your implementation looks great. I think you should submit the pull request and we will merge it. Cheers, On Feb 7, 2013, at 23:12, stevejefferies [email protected] wrote:
|
Addresses the issue described in robotframework#167.
Addresses the issue described in robotframework#167.
Fixed in #168. |
Currently S2L allows the verification of text fields through "Textfield Should Contain" and "Textfield Value Should Be" but this doesn't work for textarea elements since these keywords resolve to a tag of "input" in _get_tag_and_contraints. I tried "Element Text Should Be" and "Element Should Contain" keywords but these don't evaluate the text value currently set since these call _get_text rather that _get_value so there doesn't appear to be a way of evaluating the text you have input into a textarea field.
I have currently implemented an additional keyword locally along the lines of:
and modified _get_tag_and_constraints to allow a tag of 'text area' which returns a tag of 'textarea' which works for my needs. (also done for exact text matches in a separate keyword).
What are your thoughts on this implementation? Is it better to have a separate set of keywords for textarea elements? Or would it be better to allow support for textarea elements within the "Textfield Should Contain" keyword (and exact match keyword)?
Happy to submit a pull request for this modification if you think it's correct.
The text was updated successfully, but these errors were encountered: