[ABTEST-561]  UI-tests in magnolia-addon-tests are failing - must be fixed Created: 29/Jan/24  Updated: 31/Jan/24  Resolved: 31/Jan/24

Status: Closed
Project: A/B Testing
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.2

Type: Bug Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Resolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Work Started:

 Description   

Context

All UI-tests of use-core-TF-2.0
see https://jenkins.magnolia-cms.com/job/internal/job/addon-tests/job/master

Since 12/13 failing tests are related to AB-testing - we file the ticket "here".

Very likely the failing tests are a "result" of recent changes done by Search.X

Developer notes

While tackling the issue / fixing tests, please also:

  • Raise core-TF version to 2.0-SNAPSHOT.
  • Get rid of custom page-objects-provide AddonsPageObjects - which is not required anymore. Removing it should simplify the code.


 Comments   
Comment by Christoph Meier [ 29/Jan/24 ]

Interestingly .. it is "only" contentapp#asserExists which let's fall all these tests.
When changing the code slighty oncl. removing contentapp#asserExists - it looks like all (or mostly all) tests pass again.

Generated at Sun Feb 11 22:57:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.