Page MenuHomePhabricator

Investigate moving some Wikibase tests to @group Standalone
Open, MediumPublic

Description

The Standalone PHPUnit test group can be used to “isolate” certain tests, running them in CI only for that extension, but not for other extensions. (See T221434, the test writing manual page, T225184 for an example of moving tests in an extension, and T221434#6053295 for an example of configuring CI accordingly.) We should consider moving some of our slower tests to this group, to speed up CI in other extensions. (This could also include tests in WikibaseLexeme, WikibaseMediaInfo, etc.)

Acceptance criteria🏕️🌟:

  • We’ve written an ADR explaining our decision to move tests to the standalone group
  • The ADR lists the criteria for choosing specific tests to move (also for future reference); this probably includes “long runtime” and “low risk of breaking due to changes in other extensions”

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Addshore triaged this task as Medium priority.Jul 14 2021, 11:11 AM

Related is T287582: Move some Wikibase selenium tests to a standalone job which is to run the Wikibase Selenium tests to a dedicated job in order to stop triggering them for every other repositories. We still need a feature for developers to be able to expressly mark a test as only running when a patch affects the repository holding that test. Maybe using another npm script entry point which would make wdio to only process files in eg tests/selenium/standalone.