Background
We should define our approach to conducting manual testing in Codex.
User stories
As a Codex designer and engineer, I want to rely on a set of manual testing principles and define concrete browser/OS testing combinations in order to ensure that we offer adequate testing coverage.
Draft Documentation link
Manual testing documented in this Notion
Acceptance criteria
- We have defined our manual testing guidelines and agreed on the browser/OS testing combinations we want to test components with
- Checklist for designers to perform visual QA (similar to QTE checklist for QA T308291: Define test cases for Codex functional testing
- Necessary improvements have been made to the Codex demo site to support testing of components in isolation T311243: Clean up the Vite sandbox
- New Codex sub-package has been created to export Codex component demos so that they can be embedded in the VueTest MediaWiki extension T318842: Enable embedding of Codex component demos inside of VueTest MediaWiki extension
- Necessary improvements have been made to the VueTest extension to support the testing of components within MediaWiki: T287044: Determine how to perform QA testing of Codex components inside a MediaWiki environment
- Guidelines have been subjected to appropriate cross-team review T312113: QTE team review & publishing: manual testing guidelines
- Final Manual Testing guidelines are published in an appropriate location (either on Codex site or on a dedicated MediaWiki page under Design Systems Team).