Page MenuHomePhabricator

Provide a CI mechanism by which we can assert that front-end components can run independently of the MW back-end on which they rely
Open, Needs TriagePublic

Description

Right now CI runs all qunit/selenium testing infrastructure in the 'same' process as the MW server component, so it's not possible to determine if they're relying on local-only API calls that won't work externally (such as ResourceLoader bundle requests).

I'm not quite sure how a system would work that would let us test this, but it'd be a huge help for us to avoid repeating the situation we ended up with for Wikibase.

Event Timeline

Sounds like a system or integration test. Would something like train-dev be useful?

GrounderUK renamed this task from Provide a CI mechanism by which we can assert that front end components can run independently of the MW back-end on why they rely to Provide a CI mechanism by which we can assert that front-end components can run independently of the MW back-end on which they rely.Mar 23 2021, 4:17 PM

Sounds like a system or integration test. Would something like train-dev be useful?

Possibly? I was thinking of this in the opposite direction, a parallel integration alongside the one that's actually tested via quibble. 🤷🏽‍♂️