[MGNLEE-706] Phasing-out-JUnit-4-UI-tests on dx-core Created: 29/Jun/22  Updated: 18/Aug/22  Resolved: 19/Jul/22

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 2.25d
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLCE-317 Phasing-out-JUnit-4-UI-tests on ce Closed
dependency
is depended upon by ADMINCTRLG-9 Remove m5 servlet, green theme and co... Open
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Team: Foundation

 Description   

Removing / deleting old JUnit-4 based UI tests in ce of the package info.magnolia.integrationtests.uitest.*  which rely on the Magnolia m5-UI (using the infamous green screen / bridge-servlet).

See Phasing-out-JUnit-4-UI-tests spreadsheet about which tests can be deleted.

For tests which must be replaced with new scenario / new tests - make sure to file tickes for these tests - following The process of creating int. and functional tests - simplified



 Comments   
Comment by Christoph Meier [ 19/Jul/22 ]

All old, concrete UI-test-classes have been deleted from package it.info.magnolia.eeintegrationtests.uitest.
The pkg still contains abstract classes, but those can be deleted later on - better in the context of a distinct ticket.

Where we want to re-implement tests - tickets are filed.
We have for mostly all features already defined scenarios and put those into java classes.
In one case the scenarios need to be approved (marketing tags).
In another case at least one scenario needs to be defined (content tags).

For all the details about what has been deleted, what gets re-implemented, etc. please see https://docs.google.com/spreadsheets/d/1P-r0w852Ok-78C1ERlC540zXrsNrcIlCpI4B-owaoYI/edit#gid=1165207852

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