User:DWalden (WMF)/Test2wiki k8s migration/Caching

SRE and the Performance team already have some metrics in place to monitor the test2wiki roll-out (see phab:T308763#7954957). Therefore, it is not expected that QTE will have to do any extra testing of this.

Feature	Need testing?	What are the risks?	Does it have dependencies?	Existing regression or smoke testing strategy?	Does the regression/smoke testing strategy cover the dependencies?	Can it be tested on test2wiki?	Feasible to make it testable on test2wiki?
ObjectCache	No

<Feature>

Definitions

test2wiki

https://test2.wikipedia.org/wiki/Main_Page. An environment hosted on production servers but with test data, so is appropriate for testing. The code it is running is updated every Tuesday.

To find a list of extensions already installed on test2wiki, see https://test2.wikipedia.org/wiki/Special:Version.

Need testing?

Features may not need testing. For example, this might be because:

• it is not hosted on Production
• it is mainly a UI feature
• it is considered low-risk

External services?

• Inside our ecosystem like database, APIs, Parsoid
• Outside our ecosystem like third-party APIs

Back-end processing?

Including DeferredUpdates, job queue. See How_to#Find_out_if_my_feature/extension_does_back-end_processing.

External binaries?

See How_to#Find_out_if_my_feature/extension_uses_external_binaries.

Existing regression or smoke testing strategy?

This could include:

• Selenium tests (see How_to#Find_pre-existing_Selenium_tests)
• API tests (see How_to#Find_pre-existing_API_tests).
• Documented test procedures
• Exploratory testing