From 7b0097666db1bf56c745cdd9b18501bfcdcfc4bd Mon Sep 17 00:00:00 2001 From: Tirso Samalungo Date: Wed, 1 May 2024 21:36:40 +0100 Subject: [PATCH] Update testing-implementation-details.mdx (#515) --- content/blog/testing-implementation-details.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/testing-implementation-details.mdx b/content/blog/testing-implementation-details.mdx index 98a15b5bf..39d91d08e 100644 --- a/content/blog/testing-implementation-details.mdx +++ b/content/blog/testing-implementation-details.mdx @@ -43,7 +43,7 @@ we have to make all these rules to make it harder? ### Why is testing implementation details bad? -There are two distinct reasons that it's important to avoid testing +There are two distinct and important reasons to avoid testing implementation details. Tests which test implementation details: 1. Can break when you refactor application code. **False negatives**