npm downloads
Analyze and visualize download stats for npm packages and authors.
Analyze and visualize download stats for npm packages and authors.
Analyze and visualize download stats for npm packages and authors.
Analyze and visualize download stats for npm packages and authors.
Showing npm packages maintained by this author. Pick a package to open detailed download analytics.
Writing a test using proof is very similar to how you write your stories. Typically you'd start with:
A plugin that logs test results to the console.
A plugin that adds the option to skip the _actual_ test execution, but preserve the before and after side-effects of a test. This is most widely used in conjunction with the [accessibility-plugin](./accessibility) or [applitools-plugin](./applitools) to l
The majority of the configuration for `proof` is set through the `proof.config.js` file in the root of your project.
Uses [`axe`](https://www.deque.com/axe/) to scan each story against accessibility rules. Violatons are printed to the console, and included in any reports.
A plugin to add an empty test for each untested storybook story.
A plugin to enable babel as a test preprocessor, allowing the use of ES6/ESNext features while authoring. The default configuration uses `@babel/preset-env`
A plugin that outputs test results in the JUnit XML format.
Uses [applitools](https://applitools.com/) Visual Grid to take a snapshot of your story and run a visual regression check. It can be configured to run on may different screen-size and browser combinations. Make sure the `APPLITOOLS_ID` environment variabl
Provides Proof with visual regression testing capabilities by porting over functionality from (jest-image-snapshot)[https://github.com/americanexpress/jest-image-snapshot].
Analyze and visualize download stats for npm packages and authors.
Showing npm packages maintained by this author. Pick a package to open detailed download analytics.
Writing a test using proof is very similar to how you write your stories. Typically you'd start with:
A plugin that logs test results to the console.
A plugin that adds the option to skip the _actual_ test execution, but preserve the before and after side-effects of a test. This is most widely used in conjunction with the [accessibility-plugin](./accessibility) or [applitools-plugin](./applitools) to l
The majority of the configuration for `proof` is set through the `proof.config.js` file in the root of your project.
Uses [`axe`](https://www.deque.com/axe/) to scan each story against accessibility rules. Violatons are printed to the console, and included in any reports.
A plugin to add an empty test for each untested storybook story.
A plugin to enable babel as a test preprocessor, allowing the use of ES6/ESNext features while authoring. The default configuration uses `@babel/preset-env`
A plugin that outputs test results in the JUnit XML format.
Uses [applitools](https://applitools.com/) Visual Grid to take a snapshot of your story and run a visual regression check. It can be configured to run on may different screen-size and browser combinations. Make sure the `APPLITOOLS_ID` environment variabl
Provides Proof with visual regression testing capabilities by porting over functionality from (jest-image-snapshot)[https://github.com/americanexpress/jest-image-snapshot].