User:DWalden (WMF)/Test2wiki k8s migration/Growth
| 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? |
|---|---|---|---|---|---|---|
| Echo | Yes | DeferredUpdatesJobQueueGroup | Growth team REGRESSION QA checklist | Yes | Yes | |
| GrowthExperiments | Yes | DeferredUpdatesJobQueueGroup | Growth team REGRESSION QA checklist | Yes | only a small subset of functionality can be tested | With Product approval |
| Flow | Yes | DeferredUpdatesJobQueueGroup | Growth team REGRESSION QA checklist | Yes | Yes | Probably not - Flow is in the maintenance mode |
| Recent changes/Watchlist | Yes | JobQueueGroup | Growth team REGRESSION QA checklist | Yes | Yes | |
| PageTriage (Special:NewPagesFeed) | No | DeferredUpdatesJobQueueGroup | N/A | N/A | No | With Product approval |
Growth team - Echo, GrowthExperiments, Flow, PageTriage[edit]
What are the dependencies?[edit]
Does it use any external services?[edit]
Is there any back-end processing?[edit]
Does it use external binaries?[edit]
Does it read or write files on the filesystem?[edit]
Is there a regression or smoke testing strategy?[edit]
- The post-deployment testing checklist - Growth team REGRESSION QA checklist
- The testing summary GrowthExperiments QA on regression exploratory testing.
- Phab task T303479 has a comparison review for features functionality on test2wiki and testwiki.
Does it cover the dependencies mentioned above?[edit]
Can it be tested on test2wiki?[edit]
Is it feasible to make it testable on test2wiki?[edit]
What features do not need testing on test2wiki?[edit]
Currently, test2wiki is not used for testing the features/extensions listed in the table above.
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:
- 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