mirror of
https://github.com/discourse/discourse.git
synced 2026-08-06 13:08:40 +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.
38 lines
997 B
Ruby
Vendored
38 lines
997 B
Ruby
Vendored
# frozen_string_literal: true
|
|
|
|
describe EmberAssets do
|
|
describe "cache" do
|
|
after { EmberAssets.clear_cache! }
|
|
|
|
context "in development" do
|
|
before { Rails.env.stubs(:development?).returns(true) }
|
|
|
|
it "cache works, and is cleared before/after each web request" do
|
|
EmberAssets.cache[:foo] = "bar"
|
|
expect(EmberAssets.cache[:foo]).to eq("bar")
|
|
|
|
EmberAssets.reset
|
|
|
|
expect(EmberAssets.cache[:foo]).to eq(nil)
|
|
end
|
|
end
|
|
|
|
context "in production" do
|
|
before { Rails.env.stubs(:development?).returns(false) }
|
|
|
|
it "cache works, and can be cleared" do
|
|
EmberAssets.cache[:foo] = "bar"
|
|
expect(EmberAssets.cache[:foo]).to eq("bar")
|
|
|
|
EmberAssets.reset
|
|
|
|
# In production, persists across requests
|
|
expect(EmberAssets.cache[:foo]).to eq("bar")
|
|
|
|
# But still can be manually cleared
|
|
EmberAssets.clear_cache!
|
|
expect(EmberAssets.cache[:foo]).to eq(nil)
|
|
end
|
|
end
|
|
end
|
|
end
|
