On Jan 4, 12:29 pm, Pito Salas <[email protected]> wrote: > Thanks... > > > * .rspec in your project root -- for project settings > > * ~/.rspec -- for your personal rspec preferences for all projects > > * .rspec-local in your project root -- for a dev's specific > > preferences for a project (meant to be git-ignored) > > * The SPEC_OPTS env variable > > * Any `RSpec.configure` blocks in code that is loaded at runtime > > I checked all those spots and couldn't find the culprit, yet. > > Could it be some gem that I am loading, or a version of rails or whatnot? > > I did find a .rspec in my project route but all it had in it was --colour > > Any tip on how to trouble shoot? Not that it's a big deal at all but it bugs > me that I don't understand what's going on.. > > Thanks, > > -- Pito > > p.s. Also, RSpec::configure vs. RSpec.configure ... hmm do they mean the same > thing? > p.p.s:https://github.com/pitosalas/repsurv/tree/authent
`RSpec::configure` is just an alternate syntax--you can send a message to any object using `object::message` just like you can do `object.message`. Anyhow, someone else had this issue recently: https://github.com/rspec/rspec-core/issues/754 In his case, the problem was that his project was located on his file system at a path including `gem`, which caused ALL backtrace lines to be filtered. If the filter patterns cause all lines to be filtered, RSpec prints the full backtrace, since the full backtrace is better than no backtrace. That could be happening in your case, depending on your backtrace filter patterns and the directory your project is in. The rspec-core issue I linked to above also includes some useful troubleshooting tips. HTH, Myron -- You received this message because you are subscribed to the Google Groups "rspec" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
