Last modified: 2012-10-10 20:27:51 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 T40092, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38092 - Parsoid / parserTests: Add JUnit XML test output for Jenkins integration
Parsoid / parserTests: Add JUnit XML test output for Jenkins integration
Status: RESOLVED FIXED
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Low enhancement
: ---
Assigned To: ssastry
:
Depends on:
Blocks: 40933
  Show dependency treegraph
 
Reported: 2012-06-30 08:32 UTC by Gabriel Wicke
Modified: 2012-10-10 20:27 UTC (History)
5 users (show)

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


Attachments

Description Gabriel Wicke 2012-06-30 08:32:03 UTC
Jenkins integration would make the detection of regressions more reliable and provide us with a publicly accessible record of test results.

For this, we need to provide a test output format from parserTests that JUnit understands. The PHP parser test runner supports 'Test Results (XML)' as described in http://www.phpunit.de/manual/3.6/en/logging.html and http://windyroad.org/dl/Open%20Source/JUnit.xsd.
Comment 1 Mark Holmquist 2012-08-06 18:51:45 UTC
But, we don't appear to be using anything to run tests right now. So we would either need to start using a testing framework (maybe making the test code easier to read) or build out an XML-generator library in the tests/ directory.
Comment 2 James Forrester 2012-08-06 19:25:50 UTC
Mass-moving bugs into the new 'Parsoid' product.
Comment 3 Gabriel Wicke 2012-08-06 20:12:27 UTC
Subbu has started to use Jasmine for some purely-JS tests. We could hook up Jasmine to run all test cases in parserTests.txt in all possible directions (wikitext -> html, html -> wikitext, wikitext -> wikitext rt, html -> html rt). That should give us XML output as described above.

Given that our focus will switch away from the JS implementation soonish, it might not be worth to spend too much time on this right now. More tests in a language-indenpendent format is a higher priority in any case.
Comment 4 Krinkle 2012-08-08 04:40:44 UTC
This won't be an issue anymore when the tests are run from MediaWiki built-in hooks (either in core or as an extension). Since PHPUnit already supports it and Jenkins is already using it properly that way as well.
Comment 5 Mark Holmquist 2012-10-02 21:15:52 UTC
Fixed in changeset If48e2d8d.

https://gerrit.wikimedia.org/r/25532

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


Navigation
Links