02981324ab
System tests are used to test the application from the user's point of view. To test for specific exceptions, particularly regarding authorization permissions, controller tests fit better. Another option would be to test the page displayed shows a certain text, like "Internal server error". I'm choosing controller tests because they're faster and we're basically testing the same scenario many times and we've already got a test checking what happens when users access a page raising an exception.
42 lines
1.1 KiB
Ruby
42 lines
1.1 KiB
Ruby
require "rails_helper"
|
|
|
|
describe BudgetsController do
|
|
describe "GET show" do
|
|
it "raises an error if budget slug is not found" do
|
|
expect do
|
|
get :show, params: { id: "wrong_budget" }
|
|
end.to raise_error ActiveRecord::RecordNotFound
|
|
end
|
|
|
|
it "raises an error if budget id is not found" do
|
|
expect do
|
|
get :show, params: { id: 0 }
|
|
end.to raise_error ActiveRecord::RecordNotFound
|
|
end
|
|
|
|
context "drafting budget" do
|
|
let(:budget) { create(:budget, published: false) }
|
|
|
|
it "is not accesible to guest users" do
|
|
expect do
|
|
get :show, params: { id: budget.id }
|
|
end.to raise_error(ActionController::RoutingError)
|
|
end
|
|
|
|
it "is not accesible to logged users" do
|
|
sign_in(create(:user, :level_two))
|
|
|
|
expect do
|
|
get :show, params: { id: budget.id }
|
|
end.to raise_error(ActionController::RoutingError)
|
|
end
|
|
|
|
it "is accesible to admin users", :admin do
|
|
get :show, params: { id: budget.id }
|
|
|
|
expect(response).to be_successful
|
|
end
|
|
end
|
|
end
|
|
end
|