discourse/spec/jobs/notify_moved_posts_spec.rb
Daniel Waterworth 6e161d3e75
DEV: Allow fab! without block (#24314)
The most common thing that we do with fab! is:

    fab!(:thing) { Fabricate(:thing) }

This commit adds a shorthand for this which is just simply:

    fab!(:thing)

i.e. If you omit the block, then, by default, you'll get a `Fabricate`d object using the fabricator of the same name.
2023-11-09 16:47:59 -06:00

44 lines
1.3 KiB
Ruby

# frozen_string_literal: true
RSpec.describe Jobs::NotifyMovedPosts do
it "raises an error without post_ids" do
expect { Jobs::NotifyMovedPosts.new.execute(moved_by_id: 1234) }.to raise_error(
Discourse::InvalidParameters,
)
end
it "raises an error without moved_by_id" do
expect { Jobs::NotifyMovedPosts.new.execute(post_ids: [1, 2, 3]) }.to raise_error(
Discourse::InvalidParameters,
)
end
context "with post ids" do
fab!(:p1) { Fabricate(:post) }
fab!(:p2) { Fabricate(:post, user: Fabricate(:evil_trout), topic: p1.topic) }
fab!(:p3) { Fabricate(:post, user: p1.user, topic: p1.topic) }
fab!(:admin)
let(:moved_post_notifications) do
Notification.where(notification_type: Notification.types[:moved_post])
end
it "should create two notifications" do
expect {
Jobs::NotifyMovedPosts.new.execute(post_ids: [p1.id, p2.id, p3.id], moved_by_id: admin.id)
}.to change(moved_post_notifications, :count).by(2)
end
context "when moved by one of the posters" do
it "create one notifications, because the poster is the mover" do
expect {
Jobs::NotifyMovedPosts.new.execute(
post_ids: [p1.id, p2.id, p3.id],
moved_by_id: p1.user_id,
)
}.to change(moved_post_notifications, :count).by(1)
end
end
end
end