Skip to content

Fix link to 'Don't Test the Framework' article #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rosston merged 1 commit into from
Sep 30, 2025
Merged

Fix link to 'Don't Test the Framework' article #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/tdd/third_party.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading