Skip to content

Releases: storybookjs/test-runner

v0.21.0

20 Dec 10:07
Compare
Choose a tag to compare

πŸš€ Enhancement

πŸ› Bug Fix

Authors: 3

v0.21.0-next.1

20 Dec 09:54
9cb0ec2
Compare
Choose a tag to compare
v0.21.0-next.1 Pre-release
Pre-release

πŸ› Bug Fix

Authors: 1

v0.21.0-next.0

19 Dec 15:41
b21c854
Compare
Choose a tag to compare
v0.21.0-next.0 Pre-release
Pre-release

πŸš€ Enhancement

  • Feature: Add --listTests flag from Jest #521 (@kaelig)

Authors: 1

  • Kaelig Deloumeau-Prigent (@kaelig)

v0.20.2-next.0

16 Dec 09:34
eb1a945
Compare
Choose a tag to compare
v0.20.2-next.0 Pre-release
Pre-release

πŸ› Bug Fix

Authors: 1

v0.20.1

02 Dec 13:48
Compare
Choose a tag to compare

πŸ› Bug Fix

Authors: 1

v0.20.0

28 Nov 10:07
Compare
Choose a tag to compare

Release Notes

Refactor: Align with Storybook 8.2 core package layout

This is a structural change that shouldn't really affect you. As long as you have the storybook dependency in your app (which you should), you're good! This change makes it so that the test-runner deduplicates Storybook dependencies, and therefore, slims down your node_modules size.

Feature: Run postVisit on failures (#494)

The test-runner's postVisit hook now runs even if there are failures. This allows you to, for instance, take snapshots on component failures. You can check whether the test has failed via the hasFailure property in the context passed to the hook:

const config: TestRunnerConfig = {
  async postVisit(_page, context) {
    if(context.hasFailure) {
      console.log('problems!')
      // do a snapshot, write a log, or anything you like
    }
  },
}

πŸš€ Enhancement

  • Feature: Run postVisit on failures #494 (@yannbf)
  • Align with Storybook 8.2 core package layout #512 (@yannbf)

πŸ“ Documentation

Authors: 6

v0.20.0-next.2

28 Nov 09:40
322bd62
Compare
Choose a tag to compare
v0.20.0-next.2 Pre-release
Pre-release

Release Notes

Feature: Run postVisit on failures (#494)

The test-runner's postVisit hook now runs even if there are failures. This allows you to, for instance, take snapshots on component failures. You can check whether the test has failed via the hasFailure property in the context passed to the hook:

const config: TestRunnerConfig = {
  async postVisit(_page, context) {
    if(context.hasFailure) {
      console.log('problems!')
      // do a snapshot, write a log, or anything you like
    }
  },
}

πŸš€ Enhancement

Authors: 1

v0.20.0-next.1

04 Nov 15:04
3a2a920
Compare
Choose a tag to compare

v0.20.0-next.0

04 Nov 14:45
69677a3
Compare
Choose a tag to compare
v0.20.0-next.0 Pre-release
Pre-release

πŸš€ Enhancement

  • Align with Storybook 8.2 core package layout #512 (@yannbf)

πŸ“ Documentation

Authors: 2

v0.19.1

15 Jul 12:02
Compare
Choose a tag to compare

πŸ› Bug Fix

Authors: 2