[CONTEDIT-585] Re-enable UI test on Content Editor module Created: 11/Aug/22  Updated: 26/Dec/23

Status: Accepted
Project: Content Editor
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Sang Ngo Huu Assignee: Quach Hao Thien
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 3d 3.5h
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by CONTEDIT-608 Re-enable UI test on Content Editor m... Open
dependency
depends upon MGNLTEST-483 PO ContentEditor requires partial fix... Selected
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)
Date of First Response:
Account:
Epic Link: 6.3 Consolidation
Story Points: 5
T-Shirt Size: Small

 Description   

This ticket was originally part of the Update to the extended maintenance version of vaadin (license for productionMode=false required!) for 6.3 - MGNLUI-7211 the tests remain old, and there is a need to re-write them. 



 Comments   
Comment by Quach Hao Thien [ 05/Oct/23 ]

Discovery

  • Revised the docker configuration with the latest configuration from dx-core-test
  • Make sure all docker containers work and healthy
  • Re-enabled the disabled test cases
  • Make sure all the test cases are passed 
    • There are 12/30 tests failing so far
Comment by Christoph Meier [ 26/Dec/23 ]

Re-enabling the tests likely will require some changes on the page object info.magnolia.test.selenium.pageobjects.ContentEditor - which does not yet reflect the latest changes of the details of the UI.

-> MGNLTEST-483

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