aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZachary Scott <e@zzak.io>2014-12-22 10:07:15 -0500
committerZachary Scott <e@zzak.io>2014-12-22 10:07:15 -0500
commiteb93e70263dd6cdd212a7264abc58f542ffd9a25 (patch)
tree7b0c626864636aa83b68ad8bc526816707d36b15
parent2526b95f202cfc786d3b93914c52264db12e5f0a (diff)
downloadrails-eb93e70263dd6cdd212a7264abc58f542ffd9a25.tar.gz
rails-eb93e70263dd6cdd212a7264abc58f542ffd9a25.tar.bz2
rails-eb93e70263dd6cdd212a7264abc58f542ffd9a25.zip
I'm sorry but I would rather not link to a 7 year old blog post [ci skip]
-rw-r--r--guides/source/testing.md2
1 files changed, 0 insertions, 2 deletions
diff --git a/guides/source/testing.md b/guides/source/testing.md
index 802268d15e..c913e9d98c 100644
--- a/guides/source/testing.md
+++ b/guides/source/testing.md
@@ -324,8 +324,6 @@ Finished tests in 0.047721s, 20.9551 tests/s, 20.9551 assertions/s.
Now, if you noticed, we first wrote a test which fails for a desired functionality, then we wrote some code which adds the functionality and finally we ensured that our test passes. This approach to software development is referred to as _Test-Driven Development_ (TDD).
-TIP: Many Rails developers practice _Test-Driven Development_ (TDD). This is an excellent way to build up a test suite that exercises every part of your application. TDD is beyond the scope of this guide, but one place to start is with [15 TDD steps to create a Rails application](http://andrzejonsoftware.blogspot.com/2007/05/15-tdd-steps-to-create-rails.html).
-
To see how an error gets reported, here's a test containing an error:
```ruby