Rails integration testing: Should we use strings or named routes in http requests?
Use the 2nd version - i.e. use the path helper methods, don't use strings. Or use a 3rd one, detailed below.

Ideally, you test your routes separately from the controller (in test/routes//spec/routes/ files). That'll test that "/users/homer/edit" indeed routes to the users#edit action. Provided your using Rails' standard resourceful routes, you don't need further tests. Anything more would be you testing that Rails works, which should be unnecessary. You want to test your app.

Secondly, the reason Rails provides path/url helper methods is that hard-coding paths/urls is a recipe for a headache should the representation of those paths ever change. For instance, a simple resources :users, as: :people in the routes file would break all your hard-coded "/users/..." paths.

Thirdly, you're simply writing homer.id. But path helpers call to_param (which you can override in your models) on the object they're passed. So you're not accurately mimicking the way the path helper methods work.

Basically, if you make a change in routes.rb, you don't want to have to update your controller tests - after all, you didn't necessarily change your controllers! You only want to update your routing tests, if you have any.

Alternatively, (edit: this is for controller tests, specifically) you can use a third version, where you specify action and params separately:

get :edit, { id: homer.to_param }


This way, you side-step both hard-coded URLs, route matching, and path/URL helpers entirely. This is probably the "cleanest" solution.