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

Feature	Need testing?	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?
VisualEditor	Yes	Yes	Some browser tests	???	Yes	N/A
WikiEditor	No	No	None	N/A	Yes	N/A
TemplateData	No	No	None	N/A	Yes	N/A
Citoid	Yes	Maybe?	None (probably?)	N/A	Yes	N/A
DiscussionTools	Yes	Yes	None	N/A	Yes	N/A

Notes

Considering User:DWalden (WMF)/Test2wiki k8s migration#Scope of change, please test:

• General editing of pages in VE
  • Ensure that after saving changes and loading the editor again, the previously saved changes are visible
  • Generating citations using Citoid
• Delivery of notifications when subscribed to a topic using DiscussionTools

Citoid features in VE depend on the backend Citoid, which in turns depends on being able to make external requests. Not sure if you want to count that as a dependency.

DiscussionTools depends on Echo, some job queue stuff, Parsoid/RESTBase, and some VE features.

VisualEditor

What are the dependencies?

Does it use any external services?

• Parsoid
• Citoid
• RESTBase

Is there any back-end processing?

No(

Does it use external binaries?

No

Does it read or write files on the filesystem?

No

Is there a regression or smoke testing strategy?

Some browser tests

Does it cover the dependencies mentioned above?

???

Can it be tested on test2wiki?

Yes

Is it feasible to make it testable on test2wiki?

N/A

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