npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

dalek-reporter-junit

v0.0.2

Published

jUnit reporter for the Dalekjs testing framework

Downloads

4

Readme

dalek-reporter-junit

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

NPM NPM

Ressources

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

Docs

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">
                <severity>pass</severity>
                <description>&lt;![CDATA[David is the favourite]]&gt;</description>
                <resource>DalekJSTest</resource>
            </variation>
            <variation start="1375125067" name="val" end="null">
                <severity>pass</severity>
                <description>&lt;![CDATA[Matt is now my favourite, bow ties are cool]]&gt;</description>
                <resource>DalekJSTest</resource>
            </variation>
        </testcase>
    </testsuite>
 </resource>

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 FreeNode.net IRC

Join the #daleksjs channel on FreeNode.net 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.

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.

DalekJS

Legal FooBar (MIT License)

Copyright (c) 2013 Sebastian Golasch

Distributed under MIT license