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.
24 lines
694 B
Ruby
24 lines
694 B
Ruby
require "rails_helper"
|
|
|
|
describe Moderation::Budgets::InvestmentsController do
|
|
before { sign_in create(:moderator).user }
|
|
|
|
describe "GET index" do
|
|
it "raises an exception when the feature is disabled" do
|
|
Setting["process.budgets"] = nil
|
|
|
|
expect { get :index }.to raise_exception(FeatureFlags::FeatureDisabled)
|
|
end
|
|
end
|
|
|
|
describe "PUT moderate" do
|
|
it "keeps query parameters while using protected redirects" do
|
|
id = create(:budget_investment).id
|
|
|
|
get :moderate, params: { resource_ids: [id], filter: "all", host: "evil.dev" }
|
|
|
|
expect(response).to redirect_to "/moderation/budget_investments?filter=all&resource_ids%5B%5D=#{id}"
|
|
end
|
|
end
|
|
end
|