[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 |
ContextAll UI-tests of use-core-TF-2.0 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 notesWhile tackling the issue / fixing tests, please also:
|
| Comments |
| Comment by Christoph Meier [ 29/Jan/24 ] |
|
Interestingly .. it is "only" contentapp#asserExists which let's fall all these tests. |