From f622f1f53c2da2ca5c6a0a105dc91dae66778c3d Mon Sep 17 00:00:00 2001 From: shukryzablah Date: Wed, 24 Mar 2021 15:32:51 -0400 Subject: [PATCH] Update index.rst (#1313) --- docs/testing/index.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/testing/index.rst b/docs/testing/index.rst index 0103779cf..877879f6f 100644 --- a/docs/testing/index.rst +++ b/docs/testing/index.rst @@ -77,13 +77,13 @@ Snapshot testing As our APIs evolve, we need to know when our changes introduce any breaking changes that might break some of the clients of our GraphQL app. -However, writing tests and replicate the same response we expect from our GraphQL application can be +However, writing tests and replicating the same response we expect from our GraphQL application can be a tedious and repetitive task, and sometimes it's easier to skip this process. Because of that, we recommend the usage of `SnapshotTest `_. -SnapshotTest let us write all this tests in a breeze, as creates automatically the ``snapshots`` for us -the first time the test is executed. +SnapshotTest lets us write all these tests in a breeze, as it automatically creates the ``snapshots`` for us +the first time the test are executed. Here is a simple example on how our tests will look if we use ``pytest``: