Advanced-Search is widely used and an essential extension currently in production. There was already one approach to setup a selenium daily test for that extension in T188742: Run tests daily targeting beta cluster for all repositories with Selenium tests but for some reason this was undone again.
I think it would make sense to re-start that initiative and have a job running to get notified early when something breaks there.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T210726 Selenium framework cleanup | |||
| Open | None | T188742 Run tests daily targeting beta cluster for all repositories with Selenium tests | |||
| Resolved | zeljkofilipin | T267360 Re-enable selenium-daily-beta-AdvancedSearch |
@WMDE-Fisch this is very easy to do. If you still want this done, I can create the patch and deploy the job. The only thing I need is a user and/or team to ping in phabricator in case the job fails and the e-mail of a person and/or a team to ping in e-mail when the job fails.
See how other jobs are configured:
Change 684469 had a related patch set uploaded (by Zfilipin; author: Zfilipin):
[integration/config@master] WIP Create selenium-daily-beta-AdvancedSearch
The job is created. I have started it. Results should be available soon.
https://integration.wikimedia.org/ci/view/selenium-daily/job/selenium-daily-beta-AdvancedSearch/
Change 684479 had a related patch set uploaded (by Zfilipin; author: Zfilipin):
[mediawiki/extensions/AdvancedSearch@master] selenium: Fix JUnit reporter
Change 684479 merged by jenkins-bot:
[mediawiki/extensions/AdvancedSearch@master] selenium: Fix JUnit reporter
@WMDE-Fisch the job is created: 684469, selenium-daily-beta-AdvancedSearch.
Please notice that not all tests are running. See 684479. I have disabled the failing tests. Feel free to enable the tests and fix them.
Change 684469 merged by jenkins-bot:
[integration/config@master] jjb: Create selenium-daily-beta-AdvancedSearch