Investigate changes to codex affecting downstream selenium tests
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	vaughnwalters
	Aug 13 2024, 4:09 PM

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.

Details

	Subject	Repo	Branch	Lines +/-
	selenium: Change selectors to account for Codex component changes	mediawiki/extensions/WikiLambda	master	+4 -10

Customize query in gerrit

Event Timeline

vaughnwalters created this task.Aug 13 2024, 4:09 PM

Restricted Application added a project: Design-System-Team. · View Herald TranscriptAug 13 2024, 4:09 PM

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

Maintenance_bot added a project: Abstract Wikipedia team.Aug 13 2024, 4:30 PM

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

gerritbot added a project: Patch-For-Review.Aug 13 2024, 6:02 PM

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!