Comments on: Testing in Rails: Part 1 - Unit Testing in Ruby http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/ Code for Coders Thu, 11 Mar 2010 02:52:49 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Why does running a Test::unit test in irb work so weirdly? | keyongtech http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/comment-page-1/#comment-1352 Why does running a Test::unit test in irb work so weirdly? | keyongtech Sun, 18 Jan 2009 16:30:44 +0000 http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/#comment-1352 [...] I have found this problem mentioned by others. For an example, see this tutorial about testing: http://www.nullislove.com/2007/11/14...sting-in-ruby/ >irb --simple-prompt >> require 'test/unit' => true >> class FirstTests < [...] [...] I have found this problem mentioned by others. For an example, see this tutorial about testing: http://www.nullislove.com/2007/11/14…sting-in-ruby/ >irb –simple-prompt >> require ‘test/unit’ => true >> class FirstTests < [...]

]]> By: Richard OnRails http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/comment-page-1/#comment-1207 Richard OnRails Fri, 11 Jul 2008 00:33:28 +0000 http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/#comment-1207 Hi Kevin, > at this point both first method and second method are defined and neither has been called Excellent (subtle) point. Thanks again for your response and for pointing me to your tutorial as well. Best wishes, Richard Hi Kevin,

> at this point both first method and second method are defined and neither has been called

Excellent (subtle) point. Thanks again for your response and for pointing me to your tutorial as well.

Best wishes,
Richard

]]> By: Kevin Skoglund http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/comment-page-1/#comment-1205 Kevin Skoglund Thu, 10 Jul 2008 19:38:47 +0000 http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/#comment-1205 @Richard: All test methods are being defined inside of a class. So they are all defined before being called—meaning before Test::Unit::TestCase runs the tests. Try wrapping your example in a Ruby class to see. Here's an example to make the point. [cc lang="ruby"] > class SomeClass > def first_method > second_method > end > > def second_method > puts "Hello" > end > end => nil # at this point both first method and second method are defined and neither has been called > sc = SomeClass.new > sc.first_method => Hello [/cc] @Richard: All test methods are being defined inside of a class. So they are all defined before being called—meaning before Test::Unit::TestCase runs the tests. Try wrapping your example in a Ruby class to see. Here’s an example to make the point.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
> class SomeClass
>   def first_method
>     second_method
>   end
>
>   def second_method
>     puts "Hello"
>   end
> end
=> nil

# at this point both first method and second method are defined and neither has been called

> sc = SomeClass.new
> sc.first_method
=> Hello
]]> By: Richard OnRails http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/comment-page-1/#comment-1204 Richard OnRails Thu, 10 Jul 2008 17:12:45 +0000 http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/#comment-1204 Well written tutorial. I have one question: Why don't the references to reverse_array fail, since that method's def had not been seen at those points? For example, I get "undefined reference ..." from the following when running ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]: say1() def say1() puts "I'm 1" end Well written tutorial. I have one question:

Why don’t the references to reverse_array fail, since that method’s def had not been seen at those points? For example, I get “undefined reference …” from the following when running ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]:

say1()

def say1()
puts “I’m 1″
end

]]> By: Kevin Skoglund http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/comment-page-1/#comment-1039 Kevin Skoglund Fri, 22 Feb 2008 23:41:49 +0000 http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/#comment-1039 A single test case will cease execution when it encounters a failure. It will then move on to the next test case. So in the "test_subtraction" example above, it will never run the test "assert(1 - 1 == 0)" because the test on the line before it fails. But it will move on and try to run the other test definitions like "test_addition". A single test case will cease execution when it encounters a failure. It will then move on to the next test case.

So in the “test_subtraction” example above, it will never run the test “assert(1 - 1 == 0)” because the test on the line before it fails. But it will move on and try to run the other test definitions like “test_addition”.

]]> By: John http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/comment-page-1/#comment-1035 John Thu, 21 Feb 2008 20:55:26 +0000 http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/#comment-1035 "Tests cease execution when they encounter a failure." I just ran this using Rails. It seemed to run all my tests catching multiple failures. Does this make sense? Does Rails modify testing. Thanks, John “Tests cease execution when they encounter a failure.”

I just ran this using Rails. It seemed to run all my tests catching multiple failures.

Does this make sense? Does Rails modify testing.

Thanks,

John

]]>