On Sun, Jan 30, 2011 at 9:16 AM, David Chelimsky <dchelim...@gmail.com> wrote:
> On Jan 30, 2011, at 6:00 AM, Evgeniy Dolzhenko wrote:
>
>> On 1/30/2011 2:00 PM, Tom H. wrote:
>>> Evgeniy Dolzhenko wrote in post #978481:
>>>> Do you need the full source code of an example in the log output, or
>>>> just a description?
>>> Just the description would be good so I can match up the log entries to
>>> the spec
>>>
>> RSpec.configure do |c|
>>
>> c.before do |m|
>> Rails.logger.debug "==> #{m.example.full_description}"
>> end
>>
>> end
>
> That won't work if you use one liners (`it { should do_something }`) because
> the full_description isn't generated until after the example runs.
>
> You _could_ do it in an after hook instead. I'd also include the location
> information so you can get right to the example if you need to:
>
> RSpec.configure do |c|
> c.after do |m|
> Rails.logger.debug "=== ^^ #{m.example.full_description} ^^ ==="
> Rails.logger.debug "=== ^^ #{m.example.location} ^^ ==="
> end
> end
I'm thinking this might be an interesting use case for a custom formatter.
--
Rick DeNatale
Blog: http://talklikeaduck.denhaven2.com/
Github: http://github.com/rubyredrick
Twitter: @RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
