So I just read the release notes, and learned that I needed to use this
setting...
config.infer_spec_type_from_file_location!
On Monday, June 2, 2014 6:26:58 PM UTC-7, AndyL wrote:
>
> Another note - had to add ":type => :view" and ":type => :feature" to get
> view and feature specs working.
>
> Using Rails 4.0 and Ruby 2.1.1
>
> On Monday, June 2, 2014 5:42:02 PM UTC-7, AndyL wrote:
>>
>> I was able to work around this problem by adding ':type => :controller'
>> to my controller specs. Now everything works as before.
>>
>> BTW - the problem spec resided under the "spec/controllers" directory.
>> In rspec2 the ':type => :controller' parameter was set automatically.
>>
>>
>> On Monday, June 2, 2014 1:44:01 PM UTC-7, AndyL wrote:
>>>
>>> To test subdomains in rspec2, I used a line like 'request.host =
>>> "#{@subdomain}.testdomain.com" ' in a before(:each) clause.
>>>
>>> With rspec3, it looks like there is no request object. How can I setup
>>> custom subdomains using rspec3 ??
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"rspec" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rspec/4fafa452-634d-4def-afaa-b9a34f32985b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
