[rspec-devel] [ rspec-Feature Requests-6508 ] Proper stacktrace for mocks

noreply at rubyforge.org noreply at rubyforge.org
Sun Nov 5 20:42:14 EST 2006


Feature Requests item #6508, was opened at 2006-11-05 20:42
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=3152&aid=6508&group_id=797

Category: mock module
Group: None
Status: Open
Priority: 3
Submitted By: Aslak Hellesøy (aslak_hellesoy)
Assigned to: Nobody (None)
Summary: Proper stacktrace for mocks

Initial Comment:
run failing_examples/mocking_example.rb

This produces something like:

should fail when messages are received out of order
Mock 'one two three' received :three out of order
(eval):3:in `three'
/Users/aslakhellesoy/scm/rspec/trunk/failing_examples/mocking_example.rb:22:in `should fail when messages are received out of order'

The first line of the backtrace is bad. It shouldn't be there at all. When --backtrace is on it should show the line in RSpec's code. Can be achieved with extra args to eval (or is it class_eval)

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=3152&aid=6508&group_id=797


More information about the rspec-devel mailing list