Change Details

We need to define a comprehensive testing and QA strategy for Codex (specifically, for individual components as they get added to the library). This comprehensive strategy needs to accomplish the following goals: * Define a way to manually test components in isolation as part of the development process (i.e. before release) * Define a way to manually test components in a MediaWiki environment (either before or after release) ** MW's internationalization tools can be utilized to ensure that Codex components work properly across different languages, scripts, directionalities, etc * Define standards to write/structure automated component tests (mainly run in CI and required before a new component can be merged) * Define a way to automate visual regression testing and accessibility testing

We need to define a comprehensive testing and QA strategy for Codex (specifically, for individual components as they get added to the library). This comprehensive strategy needs to accomplish the following goals: * Define a way to **manually test components in isolation** as part of the development process (i.e. before release) * Define a way to **manually test components in a MediaWiki environment** (either before or after release) ** MW's internationalization tools can be utilized to ensure that Codex components work properly across different languages, scripts, directionalities, etc * Define standards to **write/structure automated component tests** (mainly run in CI and required before a new component can be merged) * Define a way to **automate visual regression testing** and **accessibility testing**

We need to define a comprehensive testing and QA strategy for Codex (specifically, for individual components as they get added to the library). This comprehensive strategy needs to accomplish the following goals: * Define a way to **manually test components in isolation** as part of the development process (i.e. before release) * Define a way to **manually test components in a MediaWiki environment** (either before or after release) ** MW's internationalization tools can be utilized to ensure that Codex components work properly across different languages, scripts, directionalities, etc * Define standards to **write/structure automated component tests** (mainly run in CI and required before a new component can be merged) * Define a way to **automate visual regression testing** and **accessibility testing**