Last modified: 2014-11-13 14:45:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T55697, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53697 - [project] trigger browser tests from Gerrit (tracking)
[project] trigger browser tests from Gerrit (tracking)
Status: NEW
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
wmf-deployment
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: tracking
Depends on: 57560 73364 52120 53691 54383 54387 54388 54489 58401
Blocks: tracking
  Show dependency treegraph
 
Reported: 2013-09-03 07:55 UTC by Antoine "hashar" Musso (WMF)
Modified: 2014-11-13 14:45 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Antoine "hashar" Musso (WMF) 2013-09-03 07:55:54 UTC
The VisualEditor and ULS MediaWiki extensions have recently been blessed with QA browser tests.  We would need them to be in the Contint Jenkins and triggered by Zuul whenever a patchset is submitted as well as in the gate-and-submit pipeline.

That needs several step:

- describe the jobs in Jenkins
- add the triggers in Zuul configuration
Comment 1 Antoine "hashar" Musso (WMF) 2013-09-03 16:22:39 UTC
raise priority, add 'tracking' in summary.
Comment 2 Antoine "hashar" Musso (WMF) 2013-09-03 16:25:13 UTC
We will go with ULS first since we have a good experience interacting with the i18n team and they are in European timezone just like Zeljko and I.
Comment 3 Antoine "hashar" Musso (WMF) 2013-09-20 16:30:50 UTC
See also the Wiki page https://www.mediawiki.org/wiki/Continuous_integration/Browser_tests
Comment 4 Antoine "hashar" Musso (WMF) 2013-11-25 11:45:24 UTC
The Jenkins jobo template in https://gerrit.wikimedia.org/r/#/c/86868/ would let us trigger tests.
Comment 5 Antoine "hashar" Musso (WMF) 2013-12-10 19:57:40 UTC
Quick status update:

- ULS has browser tests being triggered albeit lot of tests ends up being
- MobileFrontend has a patch that has browser tests passing locally against a freshly installed wiki. Pending review / merge then I will add the browser tests.
- VisualEditor browser tests depends on some work to be done to safely start and stop a Parsoid daemon for each test.

I am focusing this week on integrating Parsoid daemon in Jenkins
Comment 6 Antoine "hashar" Musso (WMF) 2014-07-11 11:06:23 UTC
This is no more a top priority.  We have most browsertests run twice per day instead.

We will eventually managed to get them added in Gerrit, but there is a bit more work that needs to be done first.
Comment 7 Matthew Flaschen 2014-10-02 18:37:49 UTC
(In reply to Antoine "hashar" Musso from comment #6)
> This is no more a top priority.  We have most browsertests run twice per day
> instead.
> 
> We will eventually managed to get them added in Gerrit, but there is a bit
> more work that needs to be done first.

What's the status of this?  Are there any projects that have browser tests triggering on each change (even if non-voting)?

If not, can you outline the blockers?
Comment 8 Antoine "hashar" Musso (WMF) 2014-11-13 14:04:44 UTC
(In reply to Matthew Flaschen from comment #7)
<snip>
> What's the status of this?  Are there any projects that have browser tests
> triggering on each change (even if non-voting)?
> 
> If not, can you outline the blockers?

It is not hold, mostly because we lack resources to do the integration / make them faster.  On top of my head:

* make them faster
* runnable in parallel and aggregate the results
* rethink the way we setup the environment to run the browser tests, it is currently a huge shell snippet which is copy pasted in different place


Feel free to take the leadership. Zeljkof and Nik Everett would be able to assist.  I can offer reviews / guidances as well.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links