Last modified: 2014-04-18 12:23:59 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 T52876, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50876 - Jenkins: Enable optional cucumber tests for extensions
Jenkins: Enable optional cucumber tests for extensions
Status: RESOLVED INVALID
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-07 00:49 UTC by Carl Fürstenberg
Modified: 2014-04-18 12:23 UTC (History)
3 users (show)

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


Attachments

Description Carl Fürstenberg 2013-07-07 00:49:46 UTC
There are some extensions (LinkedWiki for example) that provides cucumber tests. 
If possible, enable some kind of execution for those.
Comment 1 Antoine "hashar" Musso (WMF) 2013-07-09 13:19:05 UTC
I have no clue what cucumber is beside the ruby testing utility. If you get a list of commands that have to be run we can get a dedicated job added to run cucumber tests on that extension.

We will also need a list of packages that needs to be installed on the Jenkins server.


I am lowering bug priority since it is only a single extension which is not installed on the Wikimedia cluster.
Comment 2 Antoine "hashar" Musso (WMF) 2014-04-18 12:23:59 UTC
Closing bug for now. If one manage to find the packages dependencies and the exact sequences of commands to run the test, we can craft a job in Jenkins for it.

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


Navigation
Links