mirror of
https://github.com/discourse/discourse.git
synced 2024-11-30 03:43:38 +08:00
ea5c3a3bdc
In AdminDashboardData we have a bunch of problem checks implemented as methods on that class. This PR absolves it of the responsibility by promoting each of those checks to a first class ProblemCheck. This way each of them can have their own priority and arbitrary functionality can be isolated in its own class. Think "extract class" refactoring over and over. Since they were all moved we can also get rid of the @@problem_syms class variable which was basically the old version of the registry now replaced by ProblemCheck.realtime. In addition AdminDashboardData::Problem value object has been entirely replaced with the new ProblemCheck::Problem (with compatible API). Lastly, I added some RSpec matchers to simplify testing of problem checks and provide helpful error messages when assertions fail.
26 lines
741 B
Ruby
26 lines
741 B
Ruby
# frozen_string_literal: true
|
|
|
|
RSpec.describe ProblemCheck::FailingEmails do
|
|
subject(:check) { described_class.new }
|
|
|
|
describe ".call" do
|
|
before { Jobs.stubs(num_email_retry_jobs: failing_jobs) }
|
|
|
|
context "when number of failing jobs is 0" do
|
|
let(:failing_jobs) { 0 }
|
|
|
|
it { expect(check).to be_chill_about_it }
|
|
end
|
|
|
|
context "when jobs are failing" do
|
|
let(:failing_jobs) { 1 }
|
|
|
|
it do
|
|
expect(check).to have_a_problem.with_priority("low").with_message(
|
|
'There are 1 email jobs that failed. Check your app.yml and ensure that the mail server settings are correct. <a href="/sidekiq/retries" target="_blank">See the failed jobs in Sidekiq</a>.',
|
|
)
|
|
end
|
|
end
|
|
end
|
|
end
|