> So we're going to leave it as raise_error for now. If you'd like to push on > this (which you're welcome to), please add a ticket to lighthouse so it's > easy to find the discussions around it. If we can get general consensus that > this would be a good move in spite of the negatives I just outlined, I'm > happy to do it.
All righty let the voting begin. https://rspec.lighthouseapp.com/projects/5645-rspec/tickets/933-add-raise_exception My current leaning is actually (re a previous comment), to add a new method raise_exception, which requires them to pass in the ExceptionClass to be raised, but feel free to discuss this suggestion at the ticket above. -r _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users