Re: [Rails] Re: No route matches error using RSpec even though route DOES match

On 7 Apr 2011, at 12:29, Phoenix Rising wrote: > Success! Cataloging here for future Googlers -- > > Section 3.2 of the Rails 3 guide to routing (http:// > guides.rubyonrails.org/routing.html) says, > > "By default dynamic segments don’t accept dots – this is because the > dot is used as a sep

[Rails] Re: No route matches error using RSpec even though route DOES match

Success! Cataloging here for future Googlers -- Section 3.2 of the Rails 3 guide to routing (http:// guides.rubyonrails.org/routing.html) says, "By default dynamic segments don’t accept dots – this is because the dot is used as a separator for formatted routes. If you need to use a dot within

[Rails] Re: No route matches error using RSpec even though route DOES match

All right, I think I figured part of this out, but it's really ...sloppy. So apparently, Rails routes don't like periods in their params. The test data I had created was created using the Faker gem, and the particular "name" attribute it created had a title of Mrs. in it, and that period is what