User:DWalden (WMF)/Test2wiki k8s migration/Community Tech

Does it use any external services?
Don't think so, apart from database.

Is there any back-end processing?
Deletes of pages with lots of revisions (greater than Manual:$wgDeleteRevisionsBatchSize, usually 1000) are done in batches via the Job queue.

Does it use external binaries?
No.

Does it read or write files on the filesystem?
When deleting or restoring files, it needs to modify the files (images, etc.) in the filestore (to at least move them from one directory to another).

Is there a regression or smoke testing strategy?
There are Selenium tests for delete and restore.

Also see User:DWalden_(WMF)/(Un)delete_associated_talk_page.

Does it cover the dependencies mentioned above?
The Selenium tests do not cover deleting/restoring files or deleting/restoring pages with lots of revisions.

Can it be tested on test2wiki?
Deletion is part of MediaWiki core and can be tested anywhere.

Is it feasible to make it testable on test2wiki?
It already is.

Does it use any external services?
No, apart from the database and (if you enable live preview) the API.

Is there any back-end processing?
No.

Does it use external binaries?
If a package called "wikidiff2" is installed on the server, it will use that to calculate the diffs.

Does it read or write files on the filesystem?
No?

Is there a regression or smoke testing strategy?
No, but see User:DWalden_(WMF)/Copy_paste_diffs.

Does it cover the dependencies mentioned above?
N/A.

Can it be tested on test2wiki?
Yes. Also, I believe Wikidiff2 is installed on all production wikis (including test2wiki).

Is it feasible to make it testable on test2wiki?
It already is.

Does it use any external services?
No, apart from database.

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?
No. But see User:DWalden_(WMF)/GlobalPreferences.

Does it cover the dependencies mentioned above?
N/A.

Can it be tested on test2wiki?
Yes.

Is it feasible to make it testable on test2wiki?
It already is.

Does it use any external services?
No.

Is there any back-end processing?
I think there must be something keeping an eye on: but haven't found where yet.
 * edits to watched pages
 * purging expired watchlist items

Does it use external binaries?
No.

Does it read or write files on the filesystem?
No.

Is there a regression or smoke testing strategy?
This Selenium test.

See also User:DWalden_(WMF)/Watchlist_Expiry.

Does it cover the dependencies mentioned above?
I don't think so.

Can it be tested on test2wiki?
Yes.

Is it feasible to make it testable on test2wiki?
It already is.

Does it use any external services?
It uses the TemplateData API.

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?
Yes.

Does it cover the dependencies mentioned above?
Yes.

Can it be tested on test2wiki?
Yes.

Is it feasible to make it testable on test2wiki?
It already is.

Does it use any external services?
It has to send emails.

Apparently it can integrate with Echo (to send notifications) and CheckUser.

Is there any back-end processing?
It uses the job queue. Possibly even DeferredUpdates.

Does it use external binaries?
No.

Does it read or write files on the filesystem?
No.

Is there a regression or smoke testing strategy?
No.

Does it cover the dependencies mentioned above?
N/A.

Can it be tested on test2wiki?
Yes, I assume so.

Is it feasible to make it testable on test2wiki?
It already is.

Does it use any external services?
Don't think so.

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 Selenium tests.

Does it cover the dependencies mentioned above?
N/A.

Can it be tested on test2wiki?
Yes.

Is it feasible to make it testable on test2wiki?
It already is.

Does it use any external services?
No?

Is there any back-end processing?
Job queue and DeferredUpdates.

Does it use external binaries?
No.

Does it read or write files on the filesystem?
No?

Is there a regression or smoke testing strategy?
No.

Does it cover the dependencies mentioned above?
N/A

Can it be tested on test2wiki?
Yes.

Is it feasible to make it testable on test2wiki?
It already is.

What features do not need testing on test2wiki?

 * SVG Translate (hosted on VPS)
 * Wikisource Export (hosted on VPS)
 * Event Metrics (hosted on VPS)