A JSHint reporter for jUnit.

npm install jshint-junit-reporter
57 downloads in the last day
187 downloads in the last week
1 240 downloads in the last month

JSHint JUnit Reporter

A JSHint output report that returns results compatible with JUnit ANT Task XML. This makes it possible to integrate the results into any reporting framework that accepts that format. I have found this particularly useful in continuous integration scenarios.

The entire JSHint run is considered a test suite and each file with failures is a test case. A failure node is added to each test case indicating the number of linting errors for that test case. The body of that node enumerates the messages.

<?xml version="1.0" encoding="utf-8"?>
<testsuite name="jshint" tests="1" failures="3" errors="0" >
    <testcase name="test.js">
        <failure message="3 JSHint Failures" >
1. line 3, char 5: Missing &quot;use strict&quot; statement.
2. line 4, char 2: Missing semicolon.
3. line 1, char 1: &apos;x&apos; is not defined.


Download the file directly on install using NPM: npm install jshint-junit-reporter


Pass the path to reporter.js to the JSHint --reporter option like this: jshint --reporter=reporter.js reporter.js

You can also use this plugin with the grunt-contrib-jshint plugin that support the reporter option using something like this in your options object:

options: {
    reporter: require('jshint-junit-reporter'),
    reporterOutput: "junit-output.xml"

Bamboo Integration

In order to hook this into Bamboo I have a 3 step test-plan:

  1. Checkout Code
  2. Build Script
  3. Read JUnit XML Files

Build Script

grunt jshint
awk '/<\?xml/{x="junit-x-"++i".xml";}{print > x;}' junit-output.xml

It takes the single xml file that is generated by jshint and breaks it up into the many small XML files with each result expected by Bamboo.

I also fill in the Working Sub-directory field with the path to my repo, which my case is grunt.

Bamboo Build Script

JUnit Parser Configuration


Simply reference the files that are generated by awk and it will pick them up.

JUnit Parser Configuration


Bamboo JSHint


The reporter API provided by JSHint provides access only to failure information. Therefore, the resulting XML will only list test cases for files that contained failures.

The number of tests containing linting faiures will be reflected in the "tests" attribute of the testsuite element. The total number of failures in those files will be reflected in the "failures" attribute.

npm loves you