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

@carits-qa/jest-html-reporters

v2.0.4

Published

Jest test results processor for generating a summary in HTML

Downloads

2

Readme

Jest reporter

npm NPM downloads license

Jest test results processor for generating a summary in HTML

example picture

Installation


  npm install @carits-qa/jest-html-reporters --save-dev

Usage


Configure Jest to process the test results by adding the following entry to the Jest config (jest.config.json):

"jest": {
  ...,
  "reporters": [
    "default",
    "@carits-qa/jest-html-reporters"
  ],
  ...
}

As you run Jest from within the terminal, a file called jest_html_reporters.html will be created within your root folder containing information about your tests.

Available Options

The options below are specific to the reporter.

| Option Name | Type | Default | Description | | :------------ | :------ | :----------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | publicPath | string | '' | specify the base path | | filename | string | jest_html_reporters.html | Filename of saved report Applies to the generated html | | expand | Boolean | false | specify whether default expand all data | | pageTitle | string | Report | specify header and page title | | logoImgPath | string | undefined | specify path of the image that will be displayed to the right of page title | | hideIcon | Boolean | false | hide default icon | | customInfos | array | undefined | show some custom data info in the report, example value [ {title: 'test1', value: 'test1'}, {title: 'test2', value: 'test2'}], you can also set value to a environment variable JEST_HTML_REPORTERS_CUSTOM_INFOS, see detail in #32 |

example add config options

...,
"reporters": [
  "default",
  ["@carits-qa/jest-html-reporters", {
    "publicPath": "./html-report",
    "filename": "report.html",
    "expand": true
  }]
]

2.x updates

  • Collapsable Test Groups

This feature regrading to #37, if a test file has many test cases, here will show a Merge Data checkbox on the expanded table. You can check it to merge data and set the merge level to control how to combine those data.

For Example merge data example

  • Attach screenshot to report

This feature regrading to #36, this package will a new method named addAttach.

/**
 *
 * @param {Buffer | string} attach
 * @param {string} description of the picture
 */
const addAttach = async (attach, description) => { ... }

There are two params of this method, description is easy to understand. The param attach referring to the image, you can pass a buffer or string, if it was a buffer the package will help you create a dir named jest-html-reporters-attach and save that buffer as a jpg image in it under the publicPath. if you have already saved the image, just pass the image's path as the attach param. Here is an Example with puppeteer.

// Example attach with **buffer**
const { addAttach } = require('@carits-qa/jest-html-reporters/helper')
const puppeteer = require('puppeteer')

describe('just examples', () => {
  test('test buffer', async () => {
    const browser = await puppeteer.launch()
    const page = await browser.newPage()
    await page.goto('https://www.google.com')
    const data = await page.screenshot()
    await browser.close()
    await addAttach(data, 'test google 1')

    expect(1).toBe(1)
  })
})
// Example attach with **string**
const { addAttach } = require('@carits-qa/jest-html-reporters/helper')
const puppeteer = require('puppeteer')
const path = require('path')

describe('just examples', () => {
  test('case string', async () => {
    const browser = await puppeteer.launch()
    const page = await browser.newPage()
    const filePath = path.resolve(__dirname, './test.jpg')
    await page.goto('https://www.google.com')
    const data = await page.screenshot({path: filePath})
    await browser.close()
    await addAttach(filePath, 'test google 2')

    expect(1).toBe(2)
  })
})

it will show like this example

  • Attach a message to the report

Allows you to add a message, log something to the report etc

/**
 *
 * @param {string} message
 */
const addMsg = async (message) => { ... }

Only one parameter is required. If you stringify an object like this JSON.stringify(object, null, 2), the object will be prettified

Here is an Example with Nightmare.

const { addAttach, addMsg } = require('@carits-qa/jest-html-reporters/helper')
const Nightmare = require('nightmare')
 
describe('Yet another example', () => {
  test('Both addAttach & addMsg with failure', async () => {
    const nightmare = Nightmare({ show: true })
    await addMsg(JSON.stringify({won: 1, too: 2}, null, 2))
    await nightmare
      .goto('https://duckduckgo.com')
    const s1 = await nightmare.screenshot();  
    await addAttach(s1, 'test duckduckgo 1')
    await nightmare.end();
    await addMsg(JSON.stringify(process, null, 2))
    expect(2).toEqual(1);
  }, 20000);  

  test('addMsg with success', async () => {
    await addMsg(JSON.stringify({free: 3, for: 4}, null, 2))
    expect(2).toEqual(2);
  });    
});

example

Message still displays without screenshots and with a successful test example