Comments on: Testing in Rails: Part 3 – Unit Testing Ruby Classes (cont.)

By: Kevin Skoglund

Kevin Skoglund — Thu, 28 Aug 2008 11:28:29 +0000

@skg: With assert_raise you won’t see the exception, assert_raise catches it. You should only get a passed or failed test. It sounds like your test passed.

By: skg

skg — Thu, 28 Aug 2008 11:16:18 +0000

Hi
Very Nice Tutorial.Thanks for publishing this.One thing, when i tried
assert_raise(NoMethodError) { new_car.wheels=6 }
it does not give any exceptions.Is that what expected?But if give
ret_val=assert_raise(NoMethodError) { new_car.wheels=6 }
puts ret_val then the result is
Loaded suite car_test
Started
undefined method `wheels=’ for #
.F…
Finished in 0.030879 seconds.
1) Failure:
test_colors(CarTest) [car_test.rb:57]:
is not true.
5 tests, 27 assertions, 1 failures, 0 errors

By: Richard OnRails

Richard OnRails — Fri, 11 Jul 2008 02:49:00 +0000

Hi Kevin,

This is another great chapter.

I had to wonder when I encountered:
“assert_equal(['blue', 'black', 'red', 'green'], Car.colors)”,
whether Array comparisons are order sensitive.

I’m sure you know they are, and that Sets are the easy solution. But I imagine you thought that introducing Sets would make this tutorial unnecessarily difficult for beginners.

Best wishes,
Richard