aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorutilum <oz@utilum.com>2018-07-25 20:42:45 +0200
committerutilum <oz@utilum.com>2018-07-25 20:44:40 +0200
commit2604d184ec47441736e45cfdaeb57eec40e3ea04 (patch)
treee4b7731fe2f57042b8af40ccd4932c6f1c3a57b2 /guides
parentab8847c92092a57df6433f4fc72682074359531f (diff)
downloadrails-2604d184ec47441736e45cfdaeb57eec40e3ea04.tar.gz
rails-2604d184ec47441736e45cfdaeb57eec40e3ea04.tar.bz2
rails-2604d184ec47441736e45cfdaeb57eec40e3ea04.zip
Testing Guide: unnecessary comment
This has been around as far back as I can [see](https://github.com/rails/rails/blob/5137d03cc5b2a5f0820bdcf11b0fffe5bf461470/guides/source/testing.md). No need to specify the obvious. [ci skip]
Diffstat (limited to 'guides')
-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 b3c16f3e7c..01cda8e6e4 100644
--- a/guides/source/testing.md
+++ b/guides/source/testing.md
@@ -105,7 +105,7 @@ class ArticleTest < ActiveSupport::TestCase
The `ArticleTest` class defines a _test case_ because it inherits from `ActiveSupport::TestCase`. `ArticleTest` thus has all the methods available from `ActiveSupport::TestCase`. Later in this guide, we'll see some of the methods it gives us.
Any method defined within a class inherited from `Minitest::Test`
-(which is the superclass of `ActiveSupport::TestCase`) that begins with `test_` (case sensitive) is simply called a test. So, methods defined as `test_password` and `test_valid_password` are legal test names and are run automatically when the test case is run.
+(which is the superclass of `ActiveSupport::TestCase`) that begins with `test_` is simply called a test. So, methods defined as `test_password` and `test_valid_password` are legal test names and are run automatically when the test case is run.
Rails also adds a `test` method that takes a test name and a block. It generates a normal `Minitest::Unit` test with method names prefixed with `test_`. So you don't have to worry about naming the methods, and you can write something like: