[MGNLTEST-21] Field names may conflict with preview field info Created: 18/Mar/20 Updated: 18/Oct/21 Resolved: 18/Oct/21 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jesus Alonso | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | QA&Testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: | |
| Epic Link: | core-TF-features-bugs-improvements |
| Description |
|
In a form like this:
where there are 2 Name elements, the first element is ready-only and not really used, it is not possible to set the second value. In TextField class: void setValue(String value){ WebElement input = this.driver.findElement(this.parent).findElement(byInputText()); .... } It turns out this.driver.findElement(this.parent) is finding 2 elements and so it does not work. |
| Comments |
| Comment by Christoph Meier [ 07/Jul/20 ] |
|
Maybe this one - if we consider a "fix" instead of extending the API - could be tackled together with |
| Comment by Maxime Michel [ 11/Oct/21 ] |
|
jalonso is this still relevant? |
| Comment by Jesus Alonso [ 13/Oct/21 ] |
|
I really don't know, it was long time ago. |
| Comment by Christoph Meier [ 18/Oct/21 ] |
|
Thanks jalonso for the reply. mmichel - I close this one now. |
| Comment by Christoph Meier [ 18/Oct/21 ] |
|
Closing it since it's not sure anymore what was the issue ... |