[MGNLTEST-401] Manage version of more selenium-sub-modules Created: 06/Feb/23  Updated: 17/Feb/23  Resolved: 06/Feb/23

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

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Done Votes: 0
Labels: TPR-E2E, saas
Remaining Estimate: Not Specified
Time Spent: 0.25d
Original Estimate: Not Specified

Issue Links:
Cloners
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: E2E test improvement in AdminX
Story Points: 1
Team: AdminX
Work Started:

 Description   

core-TF must manage the version of more selenium-sub-modules

Underlying reason:
In subscription-service-admin-ui - we have a spring-boot-app (SB). SB also contains a BOM of selenium (transiently). 
If subscription-service-admin-ui utilizes a selenium-module, for which we didn't manage the version in test-framework, then the selenium-BOM provided by SB kicks in. This we must avoid


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