As of Rails 5 and RSpec 3.5, controller spec files are no longer the recommended approach, instead RSpec creates files called requests. These files test the output of your controllers by testing what happens when a request is made to a given URL.
Consider the following:
rails g rspec:controller fruits
Pre-Rails 5 you would get a file like:
spec/controllers/fruits_controller_spec.rb
With Rails 5 you would get a file like:
spec/requests/fruits_request_spec.rb
The RSpec 3.5 release notes have more to say on this:
The official recommendation of the Rails team and the RSpec core team is to write request specs instead. Request specs allow you to focus on a single controller action, but unlike controller tests involve the router, the middleware stack, and both rack requests and responses. This adds realism to the test that you are writing, and helps avoid many of the issues that are common in controller specs.
Hope this helps anyone who stops by because they were trying to figure out why Rails wasn't making controller specs!