feat: throw error on unconfigured coverage when running with --coverage #166
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
self merging @shilman |
This was referenced Aug 22, 2022
Merged
Merged
Merged
|
馃殌 PR was released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release notes
Features
The test runner now throws an error when running
yarn test-storybook --coverageand the coverage is not correctly set up. This could mean that an user might be running--coveragewithout instrumenting their code with istanbul, which would lead to problems!Version
Published prerelease version:
v0.6.0-next.2Changelog
Release Notes
feat: throw error on unconfigured coverage when running with --coverage (#166)
Features
The test runner now throws an error when running
yarn test-storybook --coverageand the coverage is not correctly set up. This could mean that an user might be running--coveragewithout instrumenting their code with istanbul, which would lead to problems!feat: add console logs on test failure (#157)
Features
feat: add console logs on test failure
This version adds console logs to the output of failed tests, in order to as provide as much information as possible to help you diagnose your issues.
feat: jest 28 support (#154)
Features
This release updates
jest-playwrightto version 2.0.0 which adds support for Jest 28. In order to maintain backwards compatibility with Jest 27, you might have to take a few steps in case you are installing the test runner for the first time, or if you don't keep package locks in your project.You can find more info at https://github.com/storybookjs/test-runner#jest-27-support
馃殌 Enhancement
馃悰 Bug Fix
Authors: 2