Page MenuHomePhabricator

Set up basic infrastructure for Cypress component tests
Closed, DeclinedPublic

Description

  • Set up Cypress 10 in Codex
  • Add a simple test for TypeaheadSearch as a proof of concept

Event Timeline

Change 832271 had a related patch set uploaded (by Michael Große; author: Michael Große):

[design/codex@main] Add cypress browser test for Menu component scroll functionality

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

Change 832271 merged by jenkins-bot:

[design/codex@main] Add cypress browser test for Menu component scroll functionality

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

Change 849191 had a related patch set uploaded (by VolkerE; author: VolkerE):

[mediawiki/core@master] Update Codex from v0.2.1 to v0.2.2

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

Change 849191 merged by jenkins-bot:

[mediawiki/core@master] Update Codex from v0.2.1 to v0.2.2

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

@Catrope can you help me understand if this task is...

  • Done? If so, we can resolve.
  • In progress? If so, we can move to sprint board & mark as high priority.
  • Deprioritized? If so, we can keep in backlog & mark as lowest priority.

Thank you! 🙏

egardner triaged this task as Medium priority.Jan 23 2023, 5:19 PM

The DST engineers talked about this in our weekly meeting on February 13th, and we decided not to pursue Cypress testing for now. Instead, we decided to first explore using Pixel for visual regression testing of Codex components in MW, and then we'll evaluate whether it's worth it to set up Backstop in Codex itself. Some of this work is tracked in T291525, T326686 and T329194. Later today I'll update these tasks and/or file new ones to represent what we discussed in our meeting.

Declining this task and its parent task (T308446) for the time being; we can reopen them if we change our minds in the future and do decide to use Cypress.