**This task is currently blocked**; before we can finalize QA testing guidelines, we must develop some new infrastructure to facilitate testing of Codex components inside of a MediaWiki environment since this is where they will primarily be used in production. Once we have provided this capability, we should come back to the draft document below and ensure it reflects the new workflow.
===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 [[ https://www.notion.so/wikimediadesign/Manual-testing-guidelines-c0fad431d6e74992a238fbdaf8e34175 | this Notion ]]
===Acceptance criteria
[x] We have defined our manual testing guidelines and agreed on the browser/OS testing combinations we want to test components with
[x] Checklist for designers to perform visual QA (similar to QTE checklist for QA {T308291}
[x] Necessary improvements have been made to the Codex demo site to support testing of components in isolation {T311243}
[] New Codex sub-package has been created to export Codex component demos so that they can be embedded in the VueTest MediaWiki extension {T318842}
[] Necessary improvements have been made to the VueTest extension to support the testing of components within MediaWiki (including internationalization support): **Task TBD**, but the work should follow the plan outlined in {T287044}
[] Guidelines have been subjected to appropriate cross-team review {T312113}
[] Final Manual Testing guidelines are published in an appropriate location (either on Codex site or on a dedicated MediaWiki page under Design Systems Team).