mirror of
https://github.com/discourse/discourse.git
synced 2026-08-10 23:59:31 +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. |
||
|---|---|---|
| .. | ||
| page_objects | ||
| admin_category_management_support_spec.rb | ||
| admin_dashboard_support_section_spec.rb | ||
| core_features_spec.rb | ||
| shared_issue_spec.rb | ||
| solved_spec.rb | ||
| solved_with_tags_spec.rb | ||
| support_category_type_setup_spec.rb | ||
