aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source
diff options
context:
space:
mode:
authorEileen M. Uchitelle <eileencodes@users.noreply.github.com>2018-07-27 10:18:47 -0400
committerGitHub <noreply@github.com>2018-07-27 10:18:47 -0400
commit45903be1344992b1f0156cd88c351067bdc93726 (patch)
tree9f08b68d8100f74aebce74a5c50b722fd78876e3 /guides/source
parent046bd75b0e5f7ec35f5136ccaaec6676dc1b88cc (diff)
parent2604d184ec47441736e45cfdaeb57eec40e3ea04 (diff)
downloadrails-45903be1344992b1f0156cd88c351067bdc93726.tar.gz
rails-45903be1344992b1f0156cd88c351067bdc93726.tar.bz2
rails-45903be1344992b1f0156cd88c351067bdc93726.zip
Merge pull request #33434 from utilum/remove_testing_guide_comment
Testing Guide: unnecessary comment
Diffstat (limited to 'guides/source')
-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: