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

mocha-elk-reporter

v3.2.0

Published

Reporter for pushing mocha test results data to ELK

Downloads

7

Readme

Build Status

mocha-elk-reporter

A simple custom mocha reporter that sends Mocha Test results to Elastic search.

Purpose

  • Sending test results to Elastic Search helps collect test results over a period of time/multiple runs.
  • With Kibana you can create different visualizations to better understand the trends for test results.
  • This helps get better visibility, helps better measure reliability, understand cause of failures, measure speed etc. of the tests.

To learn more about ELK (Elastic Search, LogStash, Kibana). Click Here [https://www.elastic.co/products/kibana]

Usage

To use mocha-elk-reporter, add it as a 'devDependency' in your project

npm install --save-dev mocha-elk-reporter

Add a elk-reporter.js file to your project for your Elastic search instance

module.exports = {
  applicationName: "application name to be sent in the content of the tests",
  elasticSearchHost: "host name with port for your elastic search instance e.g. my-elasticsearch.com:9200, 10.10.1.100:9200",
  elasticSearchIndex: "indexName"
}

Mocha by default supports different kind of reporters like spec, json, etc. You can use this reporter similar to any other reporter by passing in additional command line arguments when running the tests using mocha. i.e.

--reporter mocha-elk-reporter

After you execute a test with additional parameters, you should now see data coming into your instance of ELK.

If there are issues with your configuration you should see appropriate logs associated with that

Advance Usage

Until this issue is resolved and PR merged in. If you want to use multiple reporters for your reporting needs e.g. spec, json, mocha-allure-reporter in conjunction with this reporter, you can do so with the help 'mocha multi' module.

To add that as a devDependency to your project

npm install --save-dev mocha-multi

Now you can run multiple reporters while running mocha tests uding this command

'multi="spec=- mocha-elk-reporter=-" mocha --reporter mocha-multi'

addContext Usage

If you are using mocha-multi-reporters with mochawesome and mochawesome's addContext functionality, any key-value pairs in 'value' will automatically get sent. For example here you would have myKey sent to ELK

addContext(this, { title: 'some text here', value: { myKey: "myValue" }});

You can also use addContext standalone without mochawesome using an exposed version. you call it like this:

const addContextMER = require('mocha-elk-reporter/addContext');

Then in your actual test use it with this format:

    it('it-test1', function() {
      assert.equal([1,2,3].indexOf(4), -1);
      addContextMER(this, { title: 'some text here', value: { myKey: "myValue" }});
    });