From feb9c5f42bd99d8e9e8710c4734af60e6e602d99 Mon Sep 17 00:00:00 2001 From: Francesco Rodriguez Date: Thu, 18 Oct 2012 21:37:43 -0500 Subject: remove assert_valid method from testing guide [ci skip] --- guides/source/testing.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/guides/source/testing.md b/guides/source/testing.md index b45aba8d55..2e4ada43c3 100644 --- a/guides/source/testing.md +++ b/guides/source/testing.md @@ -390,11 +390,8 @@ NOTE: Creating your own assertions is an advanced topic that we won't cover in t Rails adds some custom assertions of its own to the `test/unit` framework: -NOTE: `assert_valid(record)` has been deprecated. Please use `assert(record.valid?)` instead. - | Assertion | Purpose | | --------------------------------------------------------------------------------- | ------- | -| `assert_valid(record)` | Ensures that the passed record is valid by Active Record standards and returns any error messages if it is not.| | `assert_difference(expressions, difference = 1, message = nil) {...}` | Test numeric difference between the return value of an expression as a result of what is evaluated in the yielded block.| | `assert_no_difference(expressions, message = nil, &block)` | Asserts that the numeric result of evaluating an expression is not changed before and after invoking the passed in block.| | `assert_recognizes(expected_options, path, extras={}, message=nil)` | Asserts that the routing of the given path was handled correctly and that the parsed options (given in the expected_options hash) match path. Basically, it asserts that Rails recognizes the route given by expected_options.| -- cgit v1.2.3