4 Commits

Author	SHA1	Message	Date
Loïc Guitaut	3eaac56797	DEV: Use proper wording for contexts in specs	2022-08-04 11:05:02 +02:00
Phil Pirozhkov	493d437e79	Add RSpec 4 compatibility (#17652) ... * Remove outdated option 04078317ba * 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-28 10:27:38 +08:00
David Taylor	c9dab6fd08	DEV: Automatically require 'rails_helper' in all specs (#16077) ... It's very easy to forget to add `require 'rails_helper'` at the top of every core/plugin spec file, and omissions can cause some very confusing/sporadic errors. By setting this flag in `.rspec`, we can remove the need for `require 'rails_helper'` entirely.	2022-03-01 17:50:50 +00:00
Jarek Radosz	48b92d8897	DEV: Isolate multisite specs (#13634) ... Mixing multisite and standard specs can lead to issues (e.g. when using `fab!`) Disabled the (upcoming https://github.com/discourse/rubocop-discourse/pull/11) rubocop rule for two files that have thoroughly tangled both types of specs.	2021-07-07 18:57:42 +02:00