aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCalvin Tam <calvinyhtam@gmail.com>2014-02-03 21:09:29 +1100
committerCalvin Tam <calvinyhtam@gmail.com>2014-02-03 21:09:29 +1100
commit8f0460d7468bc5d2a63acc2494b356ac7a0d5a22 (patch)
tree52180ca7045d242cd4d5ed444725775fcb553240
parent7f8fbf7744925881fc551ed50ab7f55bbd1db28f (diff)
downloadrails-8f0460d7468bc5d2a63acc2494b356ac7a0d5a22.tar.gz
rails-8f0460d7468bc5d2a63acc2494b356ac7a0d5a22.tar.bz2
rails-8f0460d7468bc5d2a63acc2494b356ac7a0d5a22.zip
Fixed minor typo [ci skip]
-rw-r--r--guides/source/testing.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/testing.md b/guides/source/testing.md
index 33cd3e868b..169fd75cfa 100644
--- a/guides/source/testing.md
+++ b/guides/source/testing.md
@@ -339,7 +339,7 @@ NOTE: The execution of each test method stops as soon as any error or an asserti
When a test fails you are presented with the corresponding backtrace. By default
Rails filters that backtrace and will only print lines relevant to your
-application. This eliminates the framwork noise and helps to focus on your
+application. This eliminates the framework noise and helps to focus on your
code. However there are situations when you want to see the full
backtrace. simply set the `BACKTRACE` environment variable to enable this
behavior: