How could we set up an infrastructure for targeted, end-to-end functional tests for Codex.
Acceptance Criteria
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | • STH | T302348 <Platform Initiative> Release Codex in Beta (Limited Production Release) | |||
| Invalid | None | T302025 Upgrade Codex to Beta version | |||
| Invalid | None | T302038 [Epic] Define testing and QA strategy for Codex | |||
| Declined | Catrope | T308446 Set up automated functional testing skeleton for Codex | |||
| Declined | None | T310551 Set up basic infrastructure for Cypress component tests |
Create subtasks for prototypes to test internationalization, accessibility, and performance
Repeating from a Slack conv, axe is a tool that has been seen as best-of-class in the last three years. There's also a Cypress implementation.
To aid with the investigation and selection of a test tool, @zeljkofilipin from QTE did some research on this at some point and can share his findings. He can also provide some information about the QTE support available for testing tools. Perhaps a call can be arranged?
I would very much like to discuss this.
@bwang did some a11y testing with pa11y, see T301184: Add automated accessibility tests in CI to generate accessibility benchmarks for Vector and 771476.
@zeljkofilipin and I spoke about this on June 1st, and we agreed that we would create a proof of concept for Cypress component testing in Codex
We've decided not to pursue Cypress for now, see T310551#8626238 for more information