[MGNLTEST-187] Make TextareaField#setValue more robust Created: 09/Nov/21  Updated: 21/Mar/22  Resolved: 21/Mar/22

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

Type: Improvement Priority: Neutral
Reporter: Christoph Meier Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: VN-Testing, artt
Remaining Estimate: Not Specified
Time Spent: 7h
Original Estimate: Not Specified

Template:
Acceptance criteria:
[ ]* Add a self-test for the problem case - rejecting a task and setting the rejection message.
[ ]* Re-enable "restoreVersion" (MAGNOLIA-7873 seems to be fine now ... likely "fixed" with new jackrabbit version)
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)
Date of First Response:
Epic Link: core-TF-features-bugs-improvements

 Description   

It appeared that TextareaField#setValue fails in some rare cases. 
Complaining about invalid element state.

(In publication workflow, reject, when adding the rejection text).

 #setValue  fails on input.clear()



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

Reviewed (by Michael D.), integrated. 

Closing it now.

Comment by Christoph Meier [ 10/Nov/21 ]

While the "fix" prevented the throwing of an exception  - #setValue still not working for the use case which lead to that ticket.

Further research / improvement is required.

Comment by Maxime Michel [ 21/Mar/22 ]

Closing as won't do because it.info.magnolia.functionaltests.PublicationWorkflowFunctionalTests#rejectionOfPublishing is a working test, the only issue is that the name of the workflow item isn't used when rejecting the publication request.

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