From 05cbb290f34a241c6fd2ec5bd2e3da68795ebf6c Mon Sep 17 00:00:00 2001 From: Lex Berezhny Date: Tue, 21 Aug 2018 23:04:16 -0400 Subject: [PATCH] Updated Testing (markdown) --- Testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Testing.md b/Testing.md index a397b6c..29bb9cd 100644 --- a/Testing.md +++ b/Testing.md @@ -19,7 +19,7 @@ Several testing types are covered below with various do's and dont's to help you ## Integration Tests -- An integration test covers two or more units of code and at the same time makes it an integration test. +- An integration test covers two or more units of code and should avaid mocks as much as possible. - Integration tests are primarily for proving your code does what it was designed to do and that it plays well with the rest of the code in the application. - Each public facing interaction point (API, protocol, etc) should have an adequate battery of integration tests. - Every use case or feature of the application should have integration tests showing how to exercise the feature or perform the use case and the expected results of those operations. \ No newline at end of file