From e2c32d19caf9aa0d6014d8309f20bfd0595627a0 Mon Sep 17 00:00:00 2001 From: Alessandro Fazzi Date: Fri, 26 Sep 2025 08:17:06 +0000 Subject: [PATCH] Fix link to 'Don't Test the Framework' article Updated a link in the third_party.md documentation to point to an archived version since original link is broken (redirects to not relevant contents) --- docs/tdd/third_party.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tdd/third_party.md b/docs/tdd/third_party.md index f8588b6..d531180 100644 --- a/docs/tdd/third_party.md +++ b/docs/tdd/third_party.md @@ -200,7 +200,7 @@ without logical branching—then it's usually sufficient to rely on your end-to-end testing to test your wrappers, as they would surely fail if things didn't work. Testing them on their own in earnest often veers towards [testing the -framework](https://bignerdranch.com/blog/what-does-dont-test-the-framework-mean/). +framework](https://web.archive.org/web/20210124184231/https://bignerdranch.com/blog/what-does-dont-test-the-framework-mean/). ## Also, mocking gems doesn't always work