mirror of
https://github.com/discourse/discourse.git
synced 2026-08-11 02:59:07 +08:00
6df9b0b357RSpec setup becomes harder to follow at either extreme: trivial fixture wrappers hide lifecycle and intent, while forcing every named operation inline repeats low-level protocol and configuration details. This change documents and applies a test-setup hierarchy: - use `fab!`, `let`, `let!`, `subject`, and inline `Fabricate` according to lifecycle and role; - use a small example-group method when parameterized behavior gives one spec useful vocabulary; - move helpers into auto-loaded `spec/support` only when they are shared across spec files; - use fabricators and page objects for the data shapes and system-test interfaces they own. Core and plugin support files are loaded centrally by `rails_helper`, so plugin-specific support loaders are unnecessary. The migration specs encountered during the sweep are removed according to repository policy; production migrations are unchanged.
14 lines
552 B
Ruby
Vendored
14 lines
552 B
Ruby
Vendored
# frozen_string_literal: true
|
|
|
|
RSpec.describe "Enable Solved badges by default upcoming change" do
|
|
let(:badge_names) { ["Solved 1", "Solved 2", "Solved 3", "Solved 4"] }
|
|
|
|
describe "seeding the Solved badges on a new site" do
|
|
it "enables the badges by default" do
|
|
Badge.where(name: badge_names).delete_all
|
|
load Rails.root.join("plugins/discourse-solved/db/fixtures/001_badges.rb") # rubocop:disable Discourse/Plugins/UseRequireRelative
|
|
|
|
expect(Badge.where(name: badge_names).pluck(:enabled)).to all(eq(true))
|
|
end
|
|
end
|
|
end
|
