I just bisect with `rspec spec/[a-m]* spec/my/failing_spec.rb`, and then narrow it down that way. The script is a faster way to do that.
I never found debugger inspection very useful compared to bisection because the source is often very, very opaque and distant - so unless I knew what I was looking for, I never found it. On Tue, Apr 17, 2012 at 18:44, Chris Price <ch...@puppetlabs.com> wrote: > Yeah, unfortunately, commenting out large swaths and then adding back in a > little bit at a time is about the best weapon I've found to combat those > situations so far. Would love to hear if anyone has found anything better. > > > On Tue, Apr 17, 2012 at 6:41 PM, Jeff McCune <j...@puppetlabs.com> wrote: >> >> On Tue, Apr 17, 2012 at 6:11 PM, Chris Price <ch...@puppetlabs.com> wrote: >>> >>> Doh. I didn't click through to your gist before I replied. It looks >>> like you've already identified the problematic test, so most of what I >>> posted will be of no use to you. :( >> >> >> Well, I know my test works in isolation, but I don't know what other stuff >> is happening that causes it to break in the larger context, so... maybe >> it's still useful? >> >> Specifically, I'm looking for some way to figure out relatively easily >> what's different between the two scenarios of running rspec spec/ and >> running the spec file in isolation. >> >> I thought there might be a magic bullet, but I'm guessing there isn't. In >> which case I'll just dive into the debugger and start looking around at the >> state of the system, trying to find the difference between the two. >> >> Whenever I do this, I feel like I'm in a cavern with a book of matches. I >> was hoping someone had brought along a spotlight or a magelight spell or >> something... >> >> -Jeff >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Developers" group. >> To post to this group, send email to puppet-dev@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-dev+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/puppet-dev?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To post to this group, send email to puppet-dev@googlegroups.com. > To unsubscribe from this group, send email to > puppet-dev+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-dev?hl=en. -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
