[MGNLTEST-119] Form#setTextField does not reliably clear existing text Created: 17/Nov/20  Updated: 10/Nov/23  Resolved: 09/Nov/23

Status: Closed
Project: Magnolia Test Framework
Component/s: None
Affects Version/s: 1.0.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Michael Duerig Assignee: Unassigned
Resolution: Resolved Votes: 0
Labels: artt, to-verify
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File bynder.png     PNG File bynder.pngbynder230.png    
Issue Links:
dependency
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
Team: Foundation
Approved:
Yes

 Description   

Repeat the test mentioned above specifically and try to figure out what's wrong in the context of the test. Form#setTextField is stable nowadays. If not reproducible, close the ticket.

Form#setTextField sometimes fails to clear the existing text in the text field, which results in the new text being appended to the existing one.

Observed behaviour

Calling Form#setTextField("bynder230.png") on the Asset name text field sets the text to bynder.pngbynder230.png.

Expected behaviour

The text should be set to bynder230.png

Steps to reproduce

Run DamBynderUITest#uploadDownloadEditDeleteBynderAsset multiple times until this happens. Doesn't always reproduce.

Initial analysis

The problem seems to be specific to the asset upload dialogue for Bynder assets: it automatically sets an asset name upon upload whereas uploading Magnolia assets leaves the asset name field blank.



 Comments   
Comment by Christoph Meier [ 09/Nov/23 ]

should be fixed now

Generated at Mon Feb 12 07:45:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.