From b373d84fb2a3d9756f3e0276e4fb52fd2ae09afa Mon Sep 17 00:00:00 2001 From: Cody Boyko Date: Fri, 12 May 2017 20:13:18 +0000 Subject: [ci skip] Mailer fixtures in Testing guide. Update guide to clarify that mailer fixtures are not created when using the mailer generator. --- guides/source/testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'guides') diff --git a/guides/source/testing.md b/guides/source/testing.md index 71fb6fb0e8..ced88e888c 100644 --- a/guides/source/testing.md +++ b/guides/source/testing.md @@ -1406,7 +1406,7 @@ In order to test that your mailer is working as expected, you can use unit tests For the purposes of unit testing a mailer, fixtures are used to provide an example of how the output _should_ look. Because these are example emails, and not Active Record data like the other fixtures, they are kept in their own subdirectory apart from the other fixtures. The name of the directory within `test/fixtures` directly corresponds to the name of the mailer. So, for a mailer named `UserMailer`, the fixtures should reside in `test/fixtures/user_mailer` directory. -When you generated your mailer, the generator creates stub fixtures for each of the mailers actions. If you didn't use the generator, you'll have to create those files yourself. +If you generated your mailer, the generator does not create stub fixtures for the mailers actions. You'll have to create those files yourself as described above. #### The Basic Test Case -- cgit v1.2.3