v1.5.0

🚀 Improvements

• Add selector name to autoscreenshot step (#32)

v1.3.0

🚀 Improvements

• Added autoScreenshotStorybookGlobals option (can be specified in storyfile and in plugin config). (#28)

It can be specified in order to create multiple sets of autoscreenshot tests with different storybook global values

For example, with autoScreenshotStorybookGlobals is set to:

{
  "default": {},
  "light theme": {
    "theme": "light"
  },
  "dark theme": {
    "theme": "dark"
  }
}

there would be 3 screenshot tests for each story, with each having corresponding storybook globals value:

• ... Autoscreenshot default
• ... Autoscreenshot light theme
• ... Autoscreenshot dark theme

v1.2.3

🐛 Bug fixes

• fix no test found error when trying to launch testplane --storybook with explicitly set system.fileExtensions without .js extension

v1.2.2

🐛 Bug fixes

• show original error when failed to import module

v1.2.1

🐛 Bug fixes

• fix meta.url property to work with remote s3 storybook

v1.2.0

🚀 Improvements

• feat: add ability to use custom autoscreenshot selector (#21)

v1.1.0

🚀 Improvements

• feat: add unsafe option to allow other tests execution (#20)

v1.0.0

Rename to Testplane

hermione/v1.0.0

The functionality of the plugin has been completely changed.
It would be easier to delete the old version, and then install the new one.

💣 Breaking changes

• node versions less than 18.0.0 are no longer supported
• now requires hermione 8.4+, storybook 6.4+
• no longer a storybook plugin
• now connects to hermione as:

// .hermione.conf.ts
export default {
    plugins: {
        'hermione-storybook': {
            // plugin config
        },

        // other hermione plugins...
    },

    // other hermione settings...
}

(instead of hermione-storybook/hermione)

🚀 Improvements

• add ability to automatically screenshot test storybook stories
• add ability to write hermione tests inside of storybook story files (available with ts-node)

hermione/v0.2.2

🐛 Bug fixes

Reset story args when selecting the same story (#8)

Problem reproduced when you have a story with some args (for example a and b) and hermione tests for that story:

• test t1 set all args (a and b)
• test t2 set only a args

So in case when t1 will execute first then in t2 argument b will be set to value from t1 which can lead to an incorrect view of the story