[MGNLTEST-13] #setTextField on Form works for "all" kind of text fields Created: 17/Sep/19 Updated: 18/Sep/20 Resolved: 18/Sep/20 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.2 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Michael Duerig |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | QA&Testing, form-element, ui-test-fwk | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Epic Link: | core-TF-features-bugs-improvements | ||||||||
| Sprint: | TE 11 | ||||||||
| Story Points: | 5 | ||||||||
| Description |
|
New description: Currently we have the method public Form setTextField(String caption, String text) on info.magnolia.testframework.Form. The method works if the text field is has "one row" only. As soon as it it has more rows rendered as TextArea, the setter fails. Proposed Task: imho currently I see no need to support RichText specifically for UI tests. All "additional features" of the RichTextField so far will not be tested. OLD description: Provide a page object for the RichTextField, also extend the Form to to use this new object via form. Required functions on the rich text field page object:
So far I see no need to support the "more sophisticated" features of the rich text field. A Main use case: Pages app |
| Comments |
| Comment by Christoph Meier [ 14/Jan/20 ] |
|
Federico actually proposes to
Reason: Having a "one-fits-all" solution may slow-up tests. |