@carits-qa/jest-html-reporters
v2.0.4
Published
Jest test results processor for generating a summary in HTML
Downloads
2
Maintainers
Readme
Jest reporter
Jest test results processor for generating a summary in HTML
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
- 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
- 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);
});
});
Message still displays without screenshots and with a successful test