Topic on Talk:Continuous integration/Flow

Status QUnit integration

3 comments • 01:56, 8 March 2013 11 years ago

3

MWJames (talkcontribs)

As of March 2013 QUnit tests do not run through Jenkins. What is the status/timeline of having QUnit tests run through Jenkins (also for non-core extensions) similar to that of PHPunit?

Reply 20:40, 28 February 2013 11 years ago

Krinkle (talkcontribs)

We spent a lot of time coming up with a good workflow last year. This is documented on Continuous integration/Workflow specification.

In January we added linting for javascript, and as of last week the output of jshint is also consumed by Jenkins in a "Checkstyle" report (making it easier to view, as opposed to Jenkins' raw text output).

Yesterday I added running of QUnit tests (in PhantomJS) for MediaWiki core (announcement). This is being prepared for extensions as we speak, likely next week.

Next up is testing in multiple browsers through testswarm-browserstack or grunt-saucelabs.

Reply Edited by Nemo bis 20:14, 6 March 2013 11 years ago

MWJames (talkcontribs)

Fantastic, thanks for the effort. I'll try to have SMW-core running QUnits tests as soon it is enabled for non-core extensions.

Reply 01:56, 8 March 2013 11 years ago

Reply to "Status QUnit integration"