From 5c35f704d1ceca98c39b4ad3b08fee432e943afd Mon Sep 17 00:00:00 2001 From: Zachary Scott Date: Tue, 30 Dec 2014 11:07:38 -0800 Subject: [PATCH] Replace exhaustive list of methods with pointer to API docs. [ci skip] --- guides/source/testing.md | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/guides/source/testing.md b/guides/source/testing.md index 62fc8cb8ae..2d66840306 100644 --- a/guides/source/testing.md +++ b/guides/source/testing.md @@ -1144,17 +1144,7 @@ no jobs have already been executed in the scope of each test. ### Custom Assertions And Testing Jobs Inside Other Components -Active Job ships with a bunch of custom assertions that can be used to lessen -the verbosity of tests: - -| Assertion | Purpose | -| -------------------------------------- | ------- | -| `assert_enqueued_jobs(number)` | Asserts that the number of enqueued jobs matches the given number. | -| `assert_performed_jobs(number)` | Asserts that the number of performed jobs matches the given number. | -| `assert_no_enqueued_jobs { ... }` | Asserts that no jobs have been enqueued. | -| `assert_no_performed_jobs { ... }` | Asserts that no jobs have been performed. | -| `assert_enqueued_with([args]) { ... }` | Asserts that the job passed in the block has been enqueued with the given arguments. | -| `assert_performed_with([args]) { ... }`| Asserts that the job passed in the block has been performed with the given arguments. | +Active Job ships with a bunch of custom assertions that can be used to lessen the verbosity of tests. For a full list of available assertions, see the API documentation for [`ActiveJob::TestHelper`](http://api.rubyonrails.org/classes/ActiveJob/TestHelper.html). It's a good practice to ensure that your jobs correctly get enqueued or performed wherever you invoke them (e.g. inside your controllers). This is precisely where -- GitLab