Skip to content


Subversion checkout URL

You can clone with
Download ZIP
jUnit reporter for the Dalekjs testing framework
Latest commit 892a281 @asciidisco asciidisco Release v0.0.2
Failed to load latest commit information.
test Meat.
.editorconfig Meat.
.gitattributes Sync.
.gitignore Meat.
.jshintignore Meat.
.jshintrc Meat.
.travis.yml chore(travis): Removed node 0.8 Release v0.0.2 Meat. Release v0.0.2
Gruntfile.js Debugging
LICENSE-MIT Meat. chore(README): added badges
index.js fix(core): linting errors & reduced function complexity
package.json Release v0.0.2


DalekJS reporter plugin for jUnit compatible output

Build Status Build Status Dependency Status devDependency Status NPM version Coverage unstable Stories in Ready Bitdeli Badge Built with Grunt



API Docs - Trello - Code coverage - Code complexity - Contributing - User Docs - Homepage - Twitter


The jUnit reporter can produce a jUnit compatible file with the results of your testrun, this reporter enables you to use daleks testresults within a CI environment like Jenkins.

The reporter can be installed with the following command:

$ npm install dalek-reporter-junit --save-dev

The file will follow the jUnit XML format:

<?xml version="1.0" encoding="utf-8"?>
<resource name="DalekJSTest">
    <testsuite start="1375125067" name="Click - DalekJS guinea pig [Phantomjs]" end="1375125067" totalTests="0">
        <testcase start="1375125067" name="Can click a select option (OK, jQuery style, no message)" end="null" result="null">
            <variation start="1375125067" name="val" end="1375125067">
                <description>&lt;![CDATA[David is the favourite]]&gt;</description>
            <variation start="1375125067" name="val" end="null">
                <description>&lt;![CDATA[Matt is now my favourite, bow ties are cool]]&gt;</description>

By default the file will be written to report/dalek.xml, you can change this by adding a config option to the your Dalekfile

"junit-reporter": {
  "dest": "your/folder/your_file.xml"

Help Is Just A Click Away

#dalekjs on IRC

Join the #daleksjs channel on to ask questions and get help.

Google Group Mailing List

Get announcements for new releases, share your projects and ideas that are using DalekJS, and join in open-ended discussion that does not fit in to the Github issues list or StackOverflow Q&A.

For help with syntax, specific questions on how to implement a feature using DalekJS, and other Q&A items, use StackOverflow.


Ask questions about using DalekJS in specific scenarios, with specific features. For example, help with syntax, understanding how a feature works and how to override that feature, browser specific problems and so on.

Questions on StackOverflow often turn in to blog posts or issues.

Github Issues

Report issues with DalekJS, submit pull requests to fix problems, or to create summarized and documented feature requests (preferably with pull requests that implement the feature).

Please don't ask questions or seek help in the issues list. There are other, better channels for seeking assistance, like StackOverflow and the Google Groups mailing list.


Legal FooBar (MIT License)

Copyright (c) 2013 Sebastian Golasch

Distributed under MIT license

Something went wrong with that request. Please try again.