RSpec
Ruby on Rails
Ruby
method
assert
Ruby latest stable (v2_5_5)
-
1 note -
Class: Test::Unit::Assertions
- 1_8_6_287 (0)
- 1_8_7_72 (0)
- 1_8_7_330 (0)
- 1_9_1_378
- 1_9_2_180 (-11)
- 1_9_3_125 (38)
- 1_9_3_392 (0)
- 2_1_10 (0)
- 2_2_9
- 2_4_6
- 2_5_5
- 2_6_3
- What's this?
-
use_pp=
(<= v1_8_7_330)
-
add_assertion
(<= v1_8_7_330)
-
assert
(<= v2_1_10)
-
assert_block
(<= v2_1_10)
-
assert_equal
(<= v2_1_10)
-
assert_in_delta
(<= v1_8_7_330)
-
assert_instance_of
(<= v1_8_7_330)
-
assert_kind_of
(<= v1_8_7_330)
-
assert_match
(<= v1_8_7_330)
-
assert_nil
(<= v1_8_7_330)
-
assert_no_match
(<= v2_1_10)
-
assert_not_equal
(<= v2_1_10)
-
assert_nothing_raised
(<= v2_1_10)
-
assert_nothing_thrown
(<= v2_1_10)
-
assert_not_nil
(<= v2_1_10)
-
assert_not_same
(<= v2_1_10)
-
assert_not_send
(<= v2_1_10)
-
assert_operator
(<= v1_8_7_330)
-
assert_raise
(<= v2_1_10)
-
assert_raises
(<= v1_8_7_330)
-
assert_raise_with_message
(<= v2_1_10)
-
assert_respond_to
(<= v2_1_10)
-
assert_same
(<= v1_8_7_330)
-
assert_send
(<= v2_1_10)
-
assert_throw
(<= v2_1_10)
-
assert_throws
(<= v1_8_7_330)
-
build_message
(<= v2_1_10)
-
_check_exception_class
(<= v1_8_7_330)
-
_expected_exception?
(<= v1_8_7_330)
-
flunk
(<= v1_8_7_330)
-
message
(<= v2_1_10)
-
mu_pp
(<= v2_1_10)
-
_wrap_assertion
(<= v1_8_7_330)
= private
= protected
assert(test, *msgs)
public
Tests if test is true.
msg may be a String or a Proc. If msg is a String, it will be used as the failure message. Otherwise, the result of calling msg will be used as the message if the assertion fails.
If no msg is given, a default message will be used.
assert(false, "This was expected to be true")
Register or
log in
to add new notes.
szeryf -
March 11, 2010
szeryf -
March 11, 2010
0 thanks
Use message param
The message param is invaluable in case test fails – if you use it to display relevant info, you will find out what went wrong much faster.
Reworking the silly example above:
assert some_list.include?(5)
will only tell you that
<false> is not true.
which isn’t terribly helpful, is it? But if you use message like that:
assert some_list.include?(5), "some_list = #{some_list.inspect}"
the output will be:
some_list = [1, 2]. <false> is not true.
which in most cases should give you strong hints as to why the test failed.
