#ruby rails rspec

Tisikkirlir

Suppose we've got this in our controller spec: get :edit, id: r.id response.should render_template "edit" Looks perfectly clear, but don't get over-assured about it. The matcher expects the word "edit" **anywhere** in the template filename, and, if found, the example will pass. For instance, if the actual template rendered is called `no_permission_to_edit` (which clearly assumes that editing is **not** allowed), the example will still be green. A simple and straightforward **workaround** might be: response.should render_template "/edit" , which will only match templates whose names **start** from "edit". More in-depth **solution** to the problem related to vague template matching is **using the HTTP codes** to distinguish situations like allow/deny. Consider this: Controller (simplified, proof-of-concept): def edit if not permission_condition return render "no_permission_to_edit", status: :forbidden end # Allowed, render stuff as usual. ... end Spec: get :show, id: r.id response.status.should == 200 # Is allowed. get :edit, id: r.id response.status.should == 403 # Is denied. delete :destroy, id: r.id response.status.should == 403 # Is denied.

Hopefully this saves someone an hour or two.