Provide standard way to create/run QUnit tests for Gadgets and user scripts
Open, LowPublic
Actions

Assigned To

None

Authored By

	He7d3r
	May 30 2012, 8:42 PM

Description

I was thinking about creating some QUnit tests for one of my user scripts and also for a gadget, but AFAIK there is no standard way to do this.

The [[Special:JavaScriptTest/qunit]] only says "This function has not been enabled on this wiki." but maybe it should provide a way to let users to run their QUnit tests, e.g. by defining the page name of a script, or some URL param.

For example, if a wiki has some gadgets the users (mainly sysops and gadget editors) could follow links to pages such as
[[Special:JavaScriptTest/qunit/<some name related to the gadget>]]
(or use a URL param, as in "Special:JavaScriptTest/qunit?gadget=foo") as soon as a gadget is changed, to ensure the latest changes didn't broke anything.

See Also:

Details

Reference: bz37230

Related Objects
Search...

Status	Assigned	Task
Open	None	T240647 Run QUnit tests for gadgets and user scripts during edit preview
Open	None	T39230 Provide standard way to create/run QUnit tests for Gadgets and user scripts
Open	None	T71445 Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites
Open	None	T165981 Implement a prototype JavaScript review system for MediaWiki
Open	None	T22153 Implement global gadgets (WMF-wide)
Resolved	Samwilson	T153332 Investigation: Global gadgets
Open	None	T117540 Introduce global registry for gadget module identifiers
Stalled	None	T91162 RFC: Shadow namespaces
Resolved	Legoktm	T115762 Shadow namespaces at the 2016 Wikimedia Developer Summit
Open	None	T238386 Structured localization framework for gadgets

Event Timeline

• bzimport raised the priority of this task from to Low.Nov 22 2014, 12:30 AM

• bzimport added projects: MediaWiki-extensions-Gadgets, JavaScript.

• bzimport set Reference to bz37230.

• bzimport added a subscriber: Unknown Object (MLST).

He7d3r created this task.May 30 2012, 8:42 PM

One thing I'm not sure is where these tests should be defined: if a gadget has internal name "foo", but is defined on pages with different names, such as "MediaWiki:gadget-bar.js" and "MediaWiki:gadget-bar.css", where would we define the QUnit tests which would be executed when accessing

[[Special:JavaScriptTest/qunit/foo]]
Special:JavaScriptTest/qunit?gadget=foo

Should it be...

... in [[MediaWiki:Gadget-foo/QUnit.js]] ? (then it would not be very obvious for users that its code is related to [[MediaWiki:Gadget-bar.js]])
... in [[MediaWiki:Gadget-bar/QUnit.js]] (or [[MediaWiki:Gadget-bar.js/QUnit.js]]) ? (this would mean there could be more than one page where the Unit tests of a single gadget are defined - as many as the number of parts of this gadget)

What do you think?

We can probably do this once the Gadgets 2.0 infrastructure is in place...making this depend upon that.

He7d3r mentioned this in T71445: Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites.Dec 4 2014, 12:56 PM

Ricordisamoa subscribed.Jan 10 2015, 4:58 PM

Krinkle removed a subtask: T31272: Implement Gadgets 2.0.Jul 22 2015, 12:04 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 22 2015, 12:04 AM

Krinkle added a subtask: T71445: Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites.Jul 22 2015, 12:04 AM

He7d3r updated the task description. (Show Details)Jan 6 2016, 9:26 PM

He7d3r set Security to None.

He7d3r mentioned this in T53651: Auto-generated gadget code documentation.

He7d3r removed a subscriber: • wikibugs-l-list.

hashar unsubscribed.Jan 7 2016, 10:47 AM

Qgil unsubscribed.Jan 7 2016, 2:17 PM

• Catrope unsubscribed.Jan 15 2016, 11:00 PM

He7d3r mentioned this in T123174: Code from MediaWiki:Base.js removes the linebreak before "|-", breaking table on Wikisource.Jan 27 2016, 12:01 PM

TheDJ mentioned this in T171577: Develop a long term vision for community managed scripts and gadgets.Jul 25 2017, 11:22 AM

Tgr mentioned this in T187749: Make it possible to use code from an external repository for editor-controlled Javascript/CSS.Feb 19 2018, 9:15 PM

TerraCodes subscribed.Feb 19 2018, 9:24 PM

Krinkle awarded a token.Feb 19 2018, 10:14 PM

Krinkle unsubscribed.

Liuxinyu970226 awarded a token.Feb 24 2018, 12:30 PM

Liuxinyu970226 subscribed.

Capankajsmilyo subscribed.Oct 31 2018, 10:58 AM

Tgr mentioned this in T169027: Provide iframe sandboxing for rich-media extensions (defense in depth).Oct 8 2019, 9:40 AM

Amorymeltzer subscribed.Oct 11 2019, 8:17 PM

DannyS712 subscribed.Nov 14 2019, 3:53 AM

Copying what I wrote on T234661

Hi all. I've created w:en:User:Evad37/WikiUnit.js to make on-wiki unit testing of gadgets and scripts a bit easier to implement, and available when previewing or showing changes to code. Ideally this, or something like, it would become an extension. Feedback would be appreciated at https://en.wikipedia.org/wiki/Wikipedia:Interface_administrators'_noticeboard#Gadget_and_userscript_unit_testing

Enterprisey subscribed.Dec 11 2019, 5:55 AM

Evad37 mentioned this in T240647: Run QUnit tests for gadgets and user scripts during edit preview.Dec 13 2019, 12:36 AM

Evad37 added a parent task: T240647: Run QUnit tests for gadgets and user scripts during edit preview.

Xaosflux subscribed.Dec 13 2019, 3:53 AM

Izno subscribed.Dec 13 2019, 4:55 AM

Evad37 mentioned this in T240741: Security concept review for WikiUnit extension.Dec 14 2019, 4:41 AM

MarioGom subscribed.Jul 19 2021, 8:53 AM

DAlangi_WMF subscribed.Apr 18 2022, 9:54 AM

Andrybak subscribed.Jul 13 2024, 12:01 PM