Storybook: Jest code coverage with storyshots (Angular)

Created on 26 Mar 2018  路  10Comments  路  Source: storybookjs/storybook

When using imageSnapshot test with storyshots, is it possible to get accurate coverage numbers?

With renderOnly I am getting the accurate numbers:

import initStoryshots, { renderOnly } from "@storybook/addon-storyshots";

initStoryshots({
    suite: "Image storyshots",
    test: renderOnly
});

However with imageSnapshot I am getting wrong coverage numbers:

import initStoryshots, { imageSnapshot } from "@storybook/addon-storyshots";

initStoryshots({
    suite: "Image storyshots",
    test: imageSnapshot({})
});

I am generating the image snapshots on a running instance of the playground.

storyshots inactive question / support

Most helpful comment

that's a pretty aggressive stalebot

All 10 comments

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

Any updates on this please?

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

cc @igor-dv

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

cc @thomasbertet

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!

+1 for a documented way of getting code coverage output from storybook stories

that's a pretty aggressive stalebot

Was this page helpful?
0 / 5 - 0 ratings