here's some examples: 'Recurring.add_projections: weekly & non-reconcile & starting in past should update balances appropriately' FAILED expected 1001, got #<BigDecimal:22a68d4,'0.1E4',4(12)> (using .eql?) ./spec/models/recurring_spec.rb:140: ==> Oh, actually seems to work but gives the figure in Engineering notation - I wonder if there's a way to improve the readability here?
'Recurring.add projections (perform credit card payment) should calculate amount based on offset provided' FAILED expected no Exception, got #<RuntimeError: It should display this exception> ==> Actually does show exception name, but doesn't give a back trace? Is there a way to see the back trace if required? tks On Tue, Oct 7, 2008 at 1:43 PM, Pat Maddox <[EMAIL PROTECTED]> wrote: > What are you currently seeing? afaik, you should currently see all the > dots and a few F's when specs fail, and then after that you'll see > detailed failure messages including backtraces. > > Pat > > > "Greg Hauptmann" <[EMAIL PROTECTED]> writes: > > > Hi, > > > > Can I get more details in the "rake spec" output (e.g. for eql fail, what > was the actual value that was returned)??? Another example might be what the > exception > > actually is in a case the "should not raise exception" fails... > > > > Regards > > Greg > > > > _______________________________________________ > > rspec-users mailing list > > [email protected] > > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users >
_______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
