Page MenuHomePhabricator

Run Parsoid service in quibble
Open, Needs TriagePublicFeature

Description

My work in T218345: Investigate Selenium tests for validating event logging data looked promising locally until it was time to make the tests pass in CI. I've since discovered that the issue documented in T150435#3479616 is going to block further progress. I need Parsoid in Quibble so that my Selenium tests which exercise actions that happen in a VisualEditor context can run.

Looking at quibble/cmd.py#execute, perhaps after with quibble.backend.ChromeWebDriver(display=display): we could also start a Parsoid service? From setting this up locally, I think all we'd need to do is clone the parsoid repo, have a minimal config (~12 lines), and npm run start.

Details

Related Gerrit Patches:

Event Timeline

kostajh created this task.Mar 18 2019, 1:25 AM

Change 497222 had a related patch set uploaded (by Kosta Harlan; owner: Kosta Harlan):
[integration/quibble@master] [WIP] Add Parsoid to docker image and run for Selenium tests

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

kostajh changed the subtype of this task from "Task" to "Feature Request".Mar 18 2019, 2:08 AM

Change 497222 had a related patch set uploaded (by Kosta Harlan; owner: Kosta Harlan):
[integration/quibble@master] [WIP] Add Parsoid to docker image and run for Selenium tests

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

@hashar I started with an idea of how this could work but am going to put it on hold. I'm having trouble testing my specific extension locally with Quibble, and you probably have opinions and ideas of how Parsoid could be better installed in the container (or even if you're open to doing that). Let me know if you'd like to talk through it sometime.

Change 497222 abandoned by Kosta Harlan:
Add Parsoid to docker image and run for Selenium tests

Reason:
not going to be pursued, maybe with local-charts someday

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