Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
storybook-addon-specifications
Advanced tools
This addon for storybook will allow you to write tests based on your stories and display results directly inside storybook.
First, install the addon
npm install -D storybook-addon-specifications
Add this line to your addons.js
file (create this file inside your storybook config directory if needed).
import 'storybook-addon-specifications/register';
Import the specs, describe and it
functions and use it to write your tests. This example uses Enzyme and Chai to perform the testing.
The first parameter of the describe function must be the same as the story's name.
import { storiesOf } from '@kadira/storybook'
import { specs, describe, it } from 'storybook-addon-specifications'
import {mount} from "enzyme";
import expect from "expect";
const stories = storiesOf('Button', module);
stories.add('Hello World', function () {
const helloWorldStory =
<button onClick={action('Hello World')}>
Hello World
</button>;
specs(() => describe('Hello World', function () {
it('Should have the Hello World label', function () {
let output = mount(helloWorldStory);
expect(output.text()).toContain('Hello Wrld');
});
it('Should have the Hello World label', function () {
let output = mount(helloWorldStory);
expect(output.text()).toContain('Hello World');
});
}));
return helloWorldStory;
});
Note : if you use enzyme, you'll need to add the following configuration to your webpack.config.js file
externals: {
'jsdom': 'window',
'cheerio': 'window',
'react/lib/ExecutionEnvironment': true,
'react/lib/ReactContext': 'window',
'react/addons': true,
}
Writing tests directly next to the component declaration for the story is already a great thing, but it would be better if those tests can be reused with our CI.
To do that, the idea is to add to your test runner, all the files used for declaring stories. But because this addon redefine describe and it functions, you'll need some extra-configuration to make the tests pass within the test runner. You'll also need to change a little bit your stories declaration (see ./.storybook/tests/sample.ci.jest.stories.js file as an example)
You'll find in this directory examples using JEST or MOCHA.
You can use the mocking functionality of jest to switch between the real describe and it implementation of jest or the specifications addon one.
Inside .storybook, you can add a facade.js file with the following content :
import {storiesOf as storiesOfReal, action as actionReal, linkTo as linkToReal} from "@kadira/storybook"
import { specs as specsReal, describe as describeReal, it as itReal } from 'storybook-addon-specifications'
export const storiesOf = storiesOfReal;
export const action = actionReal;
export const linkTo = linkToReal;
export const specs = specsReal;
export const describe = describeReal;
export const it = itReal;
Create a mocks directory within .storybook and add also a facade.js file.
export const storiesOf = function storiesOf() {
var api = {};
api.add = ()=> { return api; };
api.addWithInfo = ()=> { return api; };
return api;
};
export const action = () => {};
export const linkTo = () => {};
export const describe = jasmine.currentEnv_.describe;
export const it = jasmine.currentEnv_.it;
Create also a jest config file with the following content :
jest.mock('./.storybook/facade');
Inside your stories file you'll use the .storybook/facade.js file for imports.
Finally add this to your jest configuration :
"jest":{
"setupFiles": [
"./path/to/your/jest/config/file.js"
],
"automock": false,
}
Create the same facade.js file than for the jest configuration
Create wherever you want a new file that will mock the storybook api
export const storiesOf = function storiesOf() {
var api = {};
api.add = ()=> { return api; };
api.addWithInfo = ()=> { return api; };
return api;
};
export const action = () => {};
export const linkTo = () => {};
export const describe = describe;
export const it = it;
Then create or add those line to a mocha config file :
import {storiesOf, action, linkTo, describe, it} from "path/to/your/mock/file";
global.storiesOf = storiesOf;
global.action = action;
global.linkTo = linkTo;
global.describe = describe;
global.it = it;
Finally add this to your mocha running script
-w test/path/to/your/config/file.js
FAQs
Add tests to your react storybook stories
The npm package storybook-addon-specifications receives a total of 1,106 weekly downloads. As such, storybook-addon-specifications popularity was classified as popular.
We found that storybook-addon-specifications demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.