mirror of
https://github.com/discourse/discourse.git
synced 2026-08-04 10:39:43 +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.
28 lines
818 B
Ruby
Vendored
28 lines
818 B
Ruby
Vendored
# frozen_string_literal: true
|
|
|
|
describe PrettyText do
|
|
let(:post) { Fabricate(:post) }
|
|
|
|
it "can spoil blocks" do
|
|
md = PrettyText.cook("[spoiler]\nmy tests fail\n[/spoiler]")
|
|
html = "<div class=\"spoiler\">\n<p>my tests fail</p>\n</div>"
|
|
|
|
expect(md).to eq(html)
|
|
end
|
|
|
|
it "can spoil inline" do
|
|
md = PrettyText.cook("I like watching [spoiler]my tests fail[/spoiler]")
|
|
html = '<p>I like watching <span class="spoiler">my tests fail</span></p>'
|
|
|
|
expect(md).to eq(html)
|
|
end
|
|
|
|
it "can replace spoilers in emails" do
|
|
md = PrettyText.cook("I like watching [spoiler]my tests fail[/spoiler]")
|
|
md = PrettyText.format_for_email(md, post)
|
|
html =
|
|
"<p>I like watching <span class=\"spoiler\"><a href=\"#{post.full_url}\">spoiler</a></span></p>"
|
|
|
|
expect(md).to eq(html)
|
|
end
|
|
end
|
