As part of the investigation of how to speed up Selenium / Web-based end-to-end tests in CI, we need to know which existing repositories are using Selenium / wdio.
Find all wdio.conf.js or equivalent Selenium configuration files in the mediawiki codebase. and report which extensions have what settings for maxInstances.
Acceptance Criteria
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T361118 [EPIC][Infra] Reduce CI test runtime for Wikibase and related extensions | |||
| Open | karapayneWMDE | T370033 [Infra][SW] Make selenium E2E tests run in parallel in CI jobs | |||
| Resolved | None | T373999 [Infra] Check which extensions are using wdio and have parallelisation enabled |
Prio Notes:
| Impact Area | Affected |
|---|---|
| production / end users | no |
| monitoring | no |
| development efforts | yes |
| onboarding efforts | no |
| additional stakeholders | no |
For your research, this is the output of me grepping the extensions and skins for maxInstances in wdio.conf.js:
$ find . -name "wdio.conf.js" | xargs grep maxInstances ./Sanctions/tests/selenium/wdio.conf.js: maxInstances: 4 ./VisualEditor/tests/selenium/wdio.conf.js: maxInstances: 4 ./TwoColConflict/tests/selenium/wdio.conf.js: maxInstances: 4 ./Popups/tests/selenium/wdio.conf.js: maxInstances: 4 ./PageTriage/tests/selenium/wdio.conf.js: maxInstances: 4, ./CodeMirror/tests/selenium/wdio.conf.js: maxInstances: 4 ./AdvancedSearch/tests/selenium/wdio.conf.js: maxInstances: 4 ./AchievementBadges/tests/selenium/wdio.conf.js: maxInstances: 4 ./IPInfo/tests/selenium/wdio.conf.js: maxInstances: 4, ./RevisionSlider/tests/selenium/wdio.conf.js: maxInstances: 4 ./Wikibase/client/data-bridge/tests/selenium/wdio.conf.js: // set maxInstances to 1; wdio will spawn 3 processes. Therefore, if you have 10 spec ./Wikibase/client/data-bridge/tests/selenium/wdio.conf.js: // files and you set maxInstances to 10, all spec files will get tested at the same time ./Wikibase/client/data-bridge/tests/selenium/wdio.conf.js: maxInstances: 1, ./Wikibase/client/data-bridge/tests/selenium/wdio.conf.js: // maxInstances can get overwritten per capability. So if you have an in-house Selenium ./Wikibase/client/data-bridge/tests/selenium/wdio.conf.js: maxInstances: 1, ./AbuseFilter/tests/selenium/wdio.conf.js: maxInstances: 4 ./ReportIncident/tests/selenium/wdio.conf.js: maxInstances: 4, ./CommunityRequests/tests/selenium/wdio.conf.js: maxInstances: 4 ./GrowthExperiments/tests/selenium/wdio.conf.js: maxInstances: 4, ./Echo/tests/selenium/wdio.conf.js: maxInstances: 4 ./CirrusSearch/tests/selenium/wdio.conf.js: maxInstances: 1, ./CirrusSearch/tests/selenium/wdio.conf.js: maxInstances: 1, ./CirrusSearch/tests/integration/config/wdio.conf.js: // set maxInstances to 1; wdio will spawn 3 processes. Therefore, if you have 10 spec ./CirrusSearch/tests/integration/config/wdio.conf.js: // files and you set maxInstances to 10, all spec files will get tested at the same time ./CirrusSearch/tests/integration/config/wdio.conf.js: maxInstances: 1, ./CirrusSearch/tests/integration/config/wdio.conf.js: // maxInstances can get overwritten per capability. So if you have an in-house Selenium ./CirrusSearch/tests/integration/config/wdio.conf.js: maxInstances: 8, ./MinervaNeue/tests/selenium/wdio.conf.js: maxInstances: 4 ./CheckUser/tests/selenium/wdio.conf.js: maxInstances: 4
| Extension | Framework |
| AbuseFilter | 4 processes |
| AchievementBadges | 4 processes |
| AdvancedSearch | 4 processes |
| CampaignEvents | not parallel |
| CheckUser | 4 processes |
| CirrusSearch | up to 8 processes |
| CodeMirror | 4 processes |
| CommunityRequests | 4 processes |
| Echo | 4 processes |
| ElectronPdfService | not parallel |
| FacetedCategory | not parallel |
| FileImporter | not parallel |
| GrowthExperiments | 4 processes for selenium, cypress not parallel |
| IPInfo | 4 processes |
| Math | not parallel |
| MinervaNeue | 4 processes |
| Newsletter | not parallel |
| PageTriage | 4 processes |
| Popups | 4 processes |
| ProofreadPage | not parallel |
| RelatedArticles | not parallel |
| ReportIncident | 4 processes |
| RevisionSlider | 4 processes |
| Sanctions | 4 processes |
| TemplateWizard | not parallel |
| TwoColConflict | 4 processes |
| VisualEditor | 4 processes |
| Wikibase | not parallel |
| WikiLambda | not parallel |
I checked this list against codesearch, and it generally looks good.
The search also turns up mediawiki core, and a data-engineering repo. Am I right in assuming those are out of scope of this ticket?
Yeah - core is excluded because we're looking at the extensions job, and the data-engineering repo doesn't run as part of the CI checks so it's not contributing to the runtime of any jobs.