User:DWalden (WMF)/Test2wiki k8s migration/Campaign Development

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?
Campaign Events yes no yes n/a yes yes, currently testable on test2wiki


Campaign Events

edit

What are the dependencies?

edit

none

Does it use any external services?

edit

only the database

Is there any back-end processing?

edit

No, not yet

Does it use external binaries?

edit

No

Does it read or write files on the filesystem?

edit

No

Is there a regression or smoke testing strategy?

edit

There are existing API tests and selenium tests

Does it cover the dependencies mentioned above?

edit

n/a

Can it be tested on test2wiki?

edit

Yes

Is it feasible to make it testable on test2wiki?

edit

Yes, it is currently testable on test2wiki. Also, in the extension we need to explicitly make it not use the central DB, because that is controlled via the $wgCampaignEventsDatabaseCluster and $wgCampaignEventsDatabaseName variables. Those settings are string|false, where false means use the local wiki database (e.g. for test wikis), and a string means use the DB/cluster with the given name (every other prod wiki). https://www.mediawiki.org/wiki/Extension:CampaignEvents#Parameters

What features do not need testing on test2wiki?

edit

Definitions

edit
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: