Page MenuHomePhabricator

Define test order for webdriver.io tests in core to speed up CI
Closed, ResolvedPublic2 Estimated Story Points

Description

By making sure we start with the slowest running tests in CI first, we can make the most out of of running them in parallel.

Acceptance criteria:

  • Make sure we start with the slowest test first
  • Document the win in time

Event Timeline

Change #1239932 had a related patch set uploaded (by Phedenskog; author: Phedenskog):

[mediawiki/core@master] selenium: Specify test order

https://gerrit.wikimedia.org/r/1239932

Together with the split for user and pages, a test run gives us in CI:

Spec Files:	 13 passed, 13 total (100% completed) in 00:00:27

Change #1240324 had a related patch set uploaded (by Phedenskog; author: Phedenskog):

[mediawiki/core@master] selenium: Run slowest test first

https://gerrit.wikimedia.org/r/1240324

Peter set the point value for this task to 2.Feb 18 2026, 11:13 PM

Change #1239932 abandoned by Phedenskog:

[mediawiki/core@master] selenium: Run slowest test first

Reason:

Replaced by https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1240324

https://gerrit.wikimedia.org/r/1239932

Change #1240324 merged by jenkins-bot:

[mediawiki/core@master] selenium: Run slowest test first

https://gerrit.wikimedia.org/r/1240324