Page MenuHomePhabricator

Decide on how to move forward with Wikidata Bridge browser testing
Open, HighPublic

Description

WARNING: There is a potential issue with the existing browser test dependencies: T294151: Reports that the ua-parser-js npm package has been "hijacked" into a coinminer (indirect dependency of Wikibase). Care should be taken when updating.

As of change I942b5dd6 browser testing has been disabled on Wikidata Bridge due to incompatibilities between WebdriverIO's sync mode and Node.js version 16+.

There are several options for moving forward with browser testing from here:

  1. Write new Selenium/Webdriver tests in the async format and rewrite existing files incrementally to async (like it was for example done in the selenium tests targeting Wikibase repo)
  2. Write new Cypress browser tests and rewrite existing files incrementally to Cypress (like it was for example done in the EntitySchema extension)
  3. Make use of some other browser testing framework

See also:

Event Timeline

Michael triaged this task as High priority.Mar 5 2024, 12:14 PM
Michael moved this task from Incoming to Tech/Ready-ish on the Wikidata-Bridge board.

While looking at T287582, I have noticed the bridge Selenium tests have been disabled since August 2023 (in package.json the script is prefixed with an @ which prevents it from being discovered by the selenium-test script).

Change #1212109 had a related patch set uploaded (by Hoo man; author: Hoo man):

[mediawiki/extensions/Wikibase@master] Indicate why Wikidata Bridge browser tests are disabled

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

Change #1212109 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Indicate why Wikidata Bridge browser tests are disabled

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