Skip to content
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

d fixed dead link and upgraded links to https in Legacy Code Section #9

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

d fixed dead link and upgraded links to https in Legacy Code Section #9

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
4 changes: 2 additions & 2 deletions legacycode/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ title: Legacy Code

Locking down legacy code is one of the major problems when trying to work on existing code. Approval tests facilitates this in a couple of ways.

1. [Producing lots of results](http://blog.approvaltests.org/2010/12/complete-unit-testing.html)
2. [Verifying large results](http://blog.approvaltests.org/2008/10/approval-tests-pictures-worth-1000...)
1. [Producing lots of results](https://blog.approvaltests.org/2010/12/complete-unit-testing.html)
2. [Verifying large results](https://blog.approvaltests.org/2008/10/approval-tests-pictures-worth-1000.html)

Here is a video of me locking down the code from LegacyCodeRetreat.