Bump @storybook/test-runner from 0.17.0 to 0.20.0

[dependabot]

Bumps @storybook/test-runner from 0.17.0 to 0.20.0.

Release notes

Sourced from @​storybook/test-runner's releases.

v0.20.0

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

• Fix tags docs #497 (@​shilman @​yannbf)

Authors: 6

• Michael Shilman (@​shilman)
• Yann Braga (@​yannbf)

v0.20.0-next.2

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!')
</tr></table> 

... (truncated)

Changelog

Sourced from @​storybook/test-runner's changelog.

v0.20.0 (Thu Nov 28 2024)

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

• Release 0.20.0 #518 (@​yannbf @​shilman)
• Feature: Run postVisit on failures #494 (@​yannbf)
• Release 0.20.0 #514 (@​yannbf runner@fv-az773-358.an51pne1gm2ejjnmkprpigk40g.dx.internal.cloudapp.net)
• Align with Storybook 8.2 core package layout #512 (@​yannbf)

📝 Documentation

• Fix tags docs #497 (@​shilman @​yannbf)

Authors: 6

• Michael Shilman (@​shilman)
• shilman (runner@fv-az1567-4.ivwpl3vsblrubjity54i0equac.phxx.internal.cloudapp.net)
• shilman (runner@fv-az2031-358.rag0t2s20xiu3oejmeweyzhkrf.bx.internal.cloudapp.net)
• shilman (runner@fv-az738-609.ayi0s4js3kfu5apuyubnvt3std.cx.internal.cloudapp.net)
• shilman (runner@fv-az773-358.an51pne1gm2ejjnmkprpigk40g.dx.internal.cloudapp.net)
• Yann Braga (@​yannbf)

---

v0.19.1 (Mon Jul 15 2024)

🐛 Bug Fix

• Release 0.19.1 #493 (@​paulgv @​yannbf)
• fix(deps): upgrade @storybook/csf to v0.1.11 #491 (@​paulgv)

... (truncated)

Commits

• 8dabc7a Bump version to: 0.20.0 [skip ci]
• c1571a8 Update CHANGELOG.md [skip ci]
• dc1e287 Merge pull request #518 from storybookjs/release/v0.20.0
• 0129a50 bring back main deps
• f2e9c05 use next deps [skip ci]
• db2c15b fix release [skip ci]
• 322bd62 Merge pull request #494 from storybookjs/post-visit-on-failures
• 3f8071b Merge branch 'next' into post-visit-on-failures
• 3a2a920 Merge pull request #514 from storybookjs/release/0.20.0
• 3b13b86 Merge branch 'main' into release/0.20.0
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by storybook-bot, a new releaser for @​storybook/test-runner since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)