You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 7-testing/7.2-snapshots.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,6 +73,6 @@ Even the Jest official documentation says this:
73
73
74
74
Consider this scenario. You worked on a component, generated a snap and pushed it. Later another dev named John made some change in the component. Now the test of the snap will fail since snap still contains the code which you wrote. John will just need to update the snapshot to make the test pass. No need to update the test case, just one command: `jest --updateSnapshot` and you are done.
75
75
76
-
*We recommend creating an __npm script__ for updating snaps. As you can see in the package.json of our boiler plate, it conatains a command called "test:update". This command go through all the test cases and will update the snap whenever it is required.*
76
+
*We recommend creating an __npm script__ for updating snaps. As you can see in the package.json of our boiler plate, it contains a command called "test:update". This command goes through all the test cases and will update the snap whenever it is required.*
77
77
78
78
__More information can be found here:__[https://facebook.github.io/jest/docs/en/snapshot-testing.html#content](https://facebook.github.io/jest/docs/en/snapshot-testing.html#content)
0 commit comments