From ec038e934099b023a142523aeb31e34506f6d1ef Mon Sep 17 00:00:00 2001 From: Andrey Krasnov <34657799+Doesntmeananything@users.noreply.github.com> Date: Mon, 20 May 2019 14:47:35 +0300 Subject: [PATCH] chore(docs): Fix typo in unit-testing (#14177) Fixes a small typo on line 210 where the phrase "so that" was used twice in a row erroneously. --- docs/docs/unit-testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/unit-testing.md b/docs/docs/unit-testing.md index a251cd9226955..55dcd423f38c8 100644 --- a/docs/docs/unit-testing.md +++ b/docs/docs/unit-testing.md @@ -207,7 +207,7 @@ Run the tests again now and it should all work! You may get a message about the snapshot being written. This is created in a `__snapshots__` directory next to your tests. If you take a look at it, you will see that it is a JSON representation of the `
` component. You should check your snapshot files -into a source control system (for example, a GitHub repo) so that so that any changes are tracked in history. +into a source control system (for example, a GitHub repo) so that any changes are tracked in history. This is particularly important to remember if you are using a continuous integration system such as Travis or CircleCI to run tests, as these will fail if the snapshot is not checked into source control.