[MGNLCE-142] Selectively run UI tests on the new vs. old UI Created: 31/Aug/18  Updated: 20/Sep/18  Resolved: 18/Sep/18

Status: Closed
Project: Community Edition
Component/s: UI tests
Affects Version/s: None
Fix Version/s: 6.0

Type: Task Priority: Neutral
Reporter: Mikaël Geljić Assignee: Michael Mühlebach
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from MGNLCE-141 Point UI tests to M5 compatibility ad... Closed
Relates
relates to MGNLCE-146 Rewrite first UI-Test (ContactsAppUIT... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Resurface theme
Sprint: Basel 155, Basel 156
Story Points: 5

 Description   
  • Run UI tests selectively on the m5 compatibility UI vs. new one
    • via annotation on UITest class?), annot. can be flipped later on
  • Still try to run/update ContactsAppUITest to the new flavor, to validate the evolution path
    • idea: strategy for old vs. new selectors
    • idea: duplicate test classes (or locators)
    • idea: drop the old ones "earlier" since they are covered on 5.7 (and file follow-up for rewrites)

Acceptance:

  • At least one test passing on the resurface UI

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