discourse/spec/lib/new_post_result_spec.rb

# frozen_string_literal: true

require "new_post_result"

RSpec.describe NewPostResult do
  it "fails by default" do
    result = NewPostResult.new(:eviltrout)
    expect(result.failed?).to eq(true)
    expect(result.success?).to eq(false)
  end
end
DEV: use #frozen_string_literal: true on all spec This change both speeds up specs (less strings to allocate) and helps catch cases where methods in Discourse are mutating inputs. Overall we will be migrating everything to use #frozen_string_literal: true it will take a while, but this is the first and safest move in this direction 2019-04-29 19:27:42 -05:00			`# frozen_string_literal: true`

DEV: Apply syntax_tree formatting to `spec/*` 2023-01-09 05:18:21 -06:00			`require "new_post_result"`
`NewPostManager` determines whether to queue a post or not 2015-03-31 11:58:56 -05:00
Add RSpec 4 compatibility (#17652) * Remove outdated option https://github.com/rspec/rspec-core/commit/04078317ba6577699d06cf4dccf014254dcde7a6 * Use the non-globally exposed RSpec syntax https://github.com/rspec/rspec-core/pull/2803 * Use the non-globally exposed RSpec syntax, cont https://github.com/rspec/rspec-core/pull/2803 * Comply to strict predicate matchers See: - https://github.com/rspec/rspec-expectations/pull/1195 - https://github.com/rspec/rspec-expectations/pull/1196 - https://github.com/rspec/rspec-expectations/pull/1277 2022-07-27 21:27:38 -05:00			`RSpec.describe NewPostResult do`
`NewPostManager` determines whether to queue a post or not 2015-03-31 11:58:56 -05:00			`it "fails by default" do`
			`result = NewPostResult.new(:eviltrout)`
			`expect(result.failed?).to eq(true)`
			`expect(result.success?).to eq(false)`
			`end`
			`end`