Page MenuHomePhabricator

Core apitests job should run extension/skin api tests as well
Open, Needs TriagePublic

Description

https://gerrit.wikimedia.org/r/c/mediawiki/core/ /768837 caused a breakage in GrowthExperiments (T303251). That would have been caught by GrowthExperiments's API testing tests, but those are not run in core's API testing job. It seems like in core's gate-and-submit we do run QUnit/Selenium tests for all enabled extensions/skins, so it would make sense to me to do the same for api-testing tests as well.

Event Timeline

kostajh renamed this task from Should core apitests job run extension/skin api tests as well? to Core apitests job should run extension/skin api tests as well.Jun 9 2022, 11:01 AM
Aklapper subscribed.

Adding missing MediaWiki-Core-Tests code project tag as Core Platform Team Initiatives (API Integration Tests) team tag is archived and its parent Platform Engineering team does not exist anymore

Bumping this request. This would be quite useful in order to verify extension functionality that is covered via api-testing tests when temp accounts are enabled, see T365676: [REPO][SW] Ensure api-testing MediaWiki extension tests pass when temp account feature flag is enabled

Bumping this request. This would be quite useful in order to verify extension functionality that is covered via api-testing tests when temp accounts are enabled, see T365676: [REPO][SW] Ensure api-testing MediaWiki extension tests pass when temp account feature flag is enabled

I did this the boring/tedious way by creating DNM patches in each repo that has api testing tests defined. That's probably good enough for now, assuming that no regressions are introduced before we enable temp accounts in CI by default.

This task would still be nice to do some day, though, to avoid surprises and be consistent with how other test types (e.g. Selenium, PHPUnit) are run.

kostajh removed a project: Temporary accounts.

Temporary accounts is no longer relevant here, as CI has temporary accounts enabled by default.