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

karma-custom-reporter

v1.1.2

Published

A Karma plugin. Report results in MSTest trx format or custom xml format.

Downloads

12

Readme

karma-custom-reporter

A Karma plugin. Report results in MSTest trx format or custom xml format.

Installation

The easiest way is to keep karma-custom-reporter as a devDependency in your package.json.

{
  "devDependencies": {
    "karma": "~0.10",
    "karma-custom-trx-reporter": "~0.1"
  }
}

You can simple do it by:

npm install karma-custom-reporter --save-dev

Configuration

// karma.conf.js
module.exports = function(config) {
  config.set({
    plugins: [
      ...
      require('karma-custom-reporter')
    ],
    
    reporters: ['progress', 'custom-trx'],

    // the default configuration
    customTrxReporter: {
            outputFile:'',
            shortTestName:false,
            asSeparateFile: false,
            separateFileName: 'custom.xml', // can be type of file
            rootElement: 'CustomSection', // can be overridden with any text
            testXmlFormater: null // syntax for this formater is like: function (xmlSectionObject, data) {} 
    }
  });
};

outputFile

The output file specifies where the xml file will be written.

shortTestName

The custom-trx reporter will attend the browser name to the test name by default.

This can be switched off with the shortTestName config property.

nameFormatter

You can provide a custom function to format the testName field of the trx.

The nameFormatter is a function with parameters (browser, result) which returns a string.

When shortTestName is true, nameFormatter is ignored.

asSeparateFile

When is set to true the reporter will generate a separate file besides the .trx file.

When is set to false (default value) the xml data will be included in .trx file under rootElement value (as element name)

separateFileName

Name of the generated file, when asSeparateFile is set to true

rootElement

The parent element name for all xml unit tests

testXmlFormater

A function for creating any custom xml format for each test

Syntax for function is function (xmlSectionObject, data) {}

Parameters:

xmlSectionObject - xmlbuilder object

data - unit test data info

data: { unitTestId, unitTestName, className, executionId, codeBase, hostName, duration, result } 
result: {fullName, description, id, log, skipped, disabled, pending, success, suite, time, executedExpectationsCount, passedExpectations, properties }

Example:

function (xmlSectionObject, data) {
  xmlSectionObject.ele('any-text')
        .attr('name', data.unitTestName)
        .attr('duration', data.duration)
        .attr('description', '${data.unitTestName} from class ${data.className} ${result.skipped ? "was skipped":""}')
} 

You can pass list of reporters as a CLI argument too:

karma start --reporters custom-trx,dots

For more information on Karma see the homepage.