From 9000e7fdc06476ddf28ddd3f6d527979da599afd Mon Sep 17 00:00:00 2001 From: funkyman3121 Date: Fri, 4 Feb 2022 12:55:08 -0500 Subject: [PATCH] Fixed typo in Testing-Rails/types-of-tests/testing_pyramid paragraph 2. --- book/types_of_tests/testing_pyramid.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/types_of_tests/testing_pyramid.md b/book/types_of_tests/testing_pyramid.md index 976e504..7a34dfe 100644 --- a/book/types_of_tests/testing_pyramid.md +++ b/book/types_of_tests/testing_pyramid.md @@ -7,7 +7,7 @@ Because of this, unit tests are usually small and fast. In the real world, these components don't exist in a vacuum: they have to interact with each other. One component may expect a collaborator to have a -particular interface when in fact it has completely different one. Even though +particular interface when in fact it has a completely different one. Even though all the tests pass, the software as a whole is broken. This is where **integration tests** come in. These tests exercise the system as