lib/test/unit/given/simple.rb in test_unit-given-0.9.0 vs lib/test/unit/given/simple.rb in test_unit-given-0.9.1

- old
+ new

@@ -134,11 +134,11 @@ # Example: # # Given { # @google = mock() # } - # When mocks_are_called + # When test_runs # Then { # @google.expects(:search).with('foo').returns('bar') # } # Given { # @my_search = Search.new(@google) @@ -148,14 +148,14 @@ # } # Then { # assert_equal 'Found bar',@result # } # And mocks_shouldve_been_called - def mocks_are_called + def test_runs lambda {} end - # Similar to #mocks_are_called, this is used to make clear what + # Similar to #test_runs, this is used to make clear what # you are testing and what the assertions are. Since many Ruby mock # frameworks do not require an explicit "verify" step, you often have tests # that have no explicit asserts, the assertions being simply that the mocks were called # as expected. This step, which is a no-op, allows you to document that you are # expecting mocks to be called. See the example in #mocks_are_called for usage.