We should have a framework for integration tests, that ensure the different components work together end-to-end. That includes the front end, the wiki, and the evaluator (orchestrator and executor).
Description
Details
Event Timeline
Change 697056 had a related patch set uploaded (by Simone Cuomo; author: Simone Cuomo):
[mediawiki/extensions/WikiLambda@master] Add selenium to Repository
Change 697056 merged by jenkins-bot:
[mediawiki/extensions/WikiLambda@master] Add initial selenium tests
To run a full end-to-end test in CI, we'd need T280070: Provide a CI mechanism by which we can test end-to-end integration between MW and back-end services, e.g. via docker-compose to be resolved first.
Change 699736 had a related patch set uploaded (by Simone Cuomo; author: Simone Cuomo):
[mediawiki/extensions/WikiLambda@master] Write a suite of user experience end-to-end integration tests
Change 702120 had a related patch set uploaded (by Zfilipin; author: Zfilipin):
[mediawiki/extensions/WikiLambda@master] selenium: Install missing npm dependencies
Change 702120 merged by jenkins-bot:
[mediawiki/extensions/WikiLambda@master] selenium: Install missing npm dependencies
Change 699736 abandoned by Simone Cuomo:
[mediawiki/extensions/WikiLambda@master] Write a suite of user experience end-to-end integration tests
Reason:
This is too old to be relevant and also would be harder to update with current code than start from scratch