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

grunt-xunit-runner

v0.1.8

Published

Grunt task for running multiple xunit dlls with all the options that xunit console provides

Downloads

21

Readme

grunt-xunit-runner

Grunt task for running multiple xunit dlls with all the options that xunit console provides. Also totals the results from each dll at the end

Getting Started

This plugin requires Grunt ~0.4.2

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-xunit-runner --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-xunit-runner');

The "xunit_runner" task

Overview

In your project's Gruntfile, add a section named xunit_runner to the data object passed into grunt.initConfig().

grunt.initConfig({
  xunit_runner: {
    options: {
      // this is the exe that I use.  but there seem  to be a couple of runners in the xunit bin
      // your options here are to either have xunit in your path or provide a
      // workingDir for xunit.
      // WARNING
      // IF you provide the workingDir you MUST make your path/to/my/test_dll.Test1.dll RELATIVE to the working dir!
      xUnit : "xunit.console.clr4.exe"
    },
    // two forms use either or
    files:{
        dlls: [
            'path/to/my/test_dll.Tests1.dll ',
            'path/to/my/test_dll.Tests1.dll ',
            'path/to/my/test_dll.Tests1.dll ',
            'path/to/my/test_dll.Tests1.dll '
        ]
    }
    TestAndConfig:[
        {
            file:'path/to/my/test_dll.Tests1.dll ',
            config:'path/to/my/test_dll.Tests1.dll.config'
        }
  }
});

Options

stdout: true,
stderr: true,
workingDir:'',
xUnit: "xunit.console.exe",
silent:'true',
teamcity:'false',
trait:'',
notrait:'',
noshadow:'',
xml:'',
html:'',
nunit:''

// the options should follow the following format // workingDir:'../../where_my_xUnit_exe_is' // relative to current dir // silent: 'true' // teamcity: 'false' // trait: 'mytrait=myvalue' // notrait: 'mytraittoexclude=myvalue' // noshadow: 'true', // xml: 'myxmlfile.xml' // html: '../../somedir/myhtml.xml' // I believe this works, if not, sorry :( // nunit: 'mynunit.txt' //?

Contributing

I started with cs_xunit the looked at msbuild and ended up with this. I'm sure there are a) better ways to do some algorithms and b) more standard ways of doing some parts. Please feel free to inform me of these as I am kind of new to some of this stuff.

Release History

0.1.4 made task fail if any tests fail. (duh)

0.1.5 moved async from devDependencies to dependencies courtesy of jgillich made path to xunit fully resolve

0.1.6 Ok this time the path to xunit should actually resolve. I screwed it up last time and I apologize.

1.7 cleaned up implementation a little bit logging is still probably terrible. added ability to list file and config incase your dll needs a config file

1.8 fixed bug when not using config