discourse/spec/models/top_menu_item_spec.rb

# frozen_string_literal: true

RSpec.describe TopMenuItem do
  before { SiteSetting.top_menu = "categories|latest" }

  let(:items) { SiteSetting.top_menu_items }

  it "has name" do
    expect(items[0].name).to eq("categories")
    expect(items[1].name).to eq("latest")
  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 20:27:42 -04:00			`# frozen_string_literal: true`

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 22:27:38 -04:00			`RSpec.describe TopMenuItem do`
correct specs 2018-04-26 03:22:09 -04:00			`before { SiteSetting.top_menu = "categories\|latest" }`
Remove use of stubs in specs. 2017-07-07 00:18:53 -04:00
adds TopMenuItem model which encapsulates top_menu parsing logic 2013-06-21 16:31:40 -04:00			`let(:items) { SiteSetting.top_menu_items }`

			`it "has name" do`
correct specs 2018-04-26 03:22:09 -04:00			`expect(items[0].name).to eq("categories")`
			`expect(items[1].name).to eq("latest")`
adds TopMenuItem model which encapsulates top_menu parsing logic 2013-06-21 16:31:40 -04:00			`end`
BUGFIX: JSON requests don't exclude categories from filters 2014-01-31 08:36:00 -05:00			`end`