Rails Ruby on Rails

Comments and changes to this ticket

• You flagged this item as spam.
  

  eightbitraptor September 23rd, 2010 @ 05:14 PM

  • no changes were found...

  • tests_should_flunk_by_default.diff 4.3 KB
• 

  Jeremy Kemper September 23rd, 2010 @ 05:43 PM

  • State changed from “new” to “wontfix”
  • Importance changed from “” to “Low”

  Thanks Matt! We've gone back one forth on fail-by-default and we keep coming back to keeping the new-user experience clean and understandable. A failing boolean is confusingly irrelevant.

• You flagged this item as spam.
  

  eightbitraptor September 23rd, 2010 @ 05:58 PM

  Thanks for the feedback. I guess that makes sense however I would argue that a misleading pass would be more harmful than a more verbose rake output. It could give a false sense of confidence that generated code is already tested for example.

  Anyway. I'm assuming this has already been argued to death so i'll let this one die.

  Matt.

• 

  Andrew White October 18th, 2010 @ 12:12 PM

  Why not use pending as a middle way?

  require 'test_helper'
  
  class PagesControllerTest < ActionController::TestCase
    test "pages controller" do
      pending "Replace this with your real tests"
    end
  end
  

  That way you don't get a backtrace and error message if you're lazy, just a single line acting as a reminder.