Page MenuHomePhabricator

Investigate changes to codex affecting downstream selenium tests
Closed, ResolvedPublic

Description

Changes made to codex can affect downstream selenium tests where the components are not in the downstream codebase. Additionally, when new codex components are added into downstream extensions, there are no data-testids available, so we have to rely on targeting classes or other elements which are more likely to change.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Change #1062450 had a related patch set uploaded (by Vaughn Walters; author: Vaughn Walters):

[mediawiki/extensions/WikiLambda@master] selenium: Changing selectors to account for codex component changes

https://gerrit.wikimedia.org/r/1062450

CCiufo-WMF subscribed.

Hey @vaughnwalters, do you need support from Design-System-Team on this task? It sounds like the immediate fix needs to happen downstream, but we welcome suggestions on how we can help make changes to Codex less disruptive in the future!

Change #1062450 merged by jenkins-bot:

[mediawiki/extensions/WikiLambda@master] selenium: Change selectors to account for Codex component changes

https://gerrit.wikimedia.org/r/1062450