GitHub/storybook
1
0
Fork 0
mirror of https://github.com/storybookjs/storybook.git synced 2025-04-05 08:01:20 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #12000 from unruthless/patch-1

Browse Source 
[Docs] Fix grammar on testing-with-storybook.md
This commit is contained in:
jonniebigodes 2020-08-13 21:07:51 +01:00 committed by GitHub
commit 12d531d8ac
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/workflows/testing-with-storybook.md
View File

@ -14,6 +14,6 @@ As you add more stories, manual testing becomes infeasible. We recommend automat
- Manual tests rely on developers to manually look at a component to verify it for correctness. They help us sanity check a component’s appearance as we build.
- [Unit tests](./unit-testing.md) verify that the output of a component remains the same given a fixed input. They’re great for testing the functional qualities of a component.
- [Visual regression tests](./visual-testing.md) capturing screenshots of every story and comparing them against known baselines. They’re great for catching UI appearance bugs.
- [Interaction tests](./interaction-testing.md) will render a story and then interact with it in the browser, asserting things about the way it renders and changes.
- [Visual regression tests](./visual-testing.md) capture screenshots of every story and compare them against known baselines. They’re great for catching UI appearance bugs.
- [Interaction tests](./interaction-testing.md) render a story and then interact with it in the browser, asserting things about the way it renders and changes.
- [Snapshot tests](./snapshot-testing.md) compare the rendered markup of every story against known baselines. This catches markup changes that cause rendering errors and warnings.