We’ve just included what we call smoke specs or core features specs in both skeletons for plugins and themes. These specs ensure the plugin or the theme you’re working on doesn’t break the basic functionality of Discourse. It’s easy to add these specs to an existing plugin or theme: For a plugin # spec/system/core_features_spec.rb RSpec.describe "Core features", type: :system do before { enable_current_plugin } it_behaves_like "having working core features" end For a theme # spec/system/core_features_spec.rb RSpec.describe "Core features", type: :system do before { upload_theme_or_component } it_behaves_like "having working core features" end If you need to update many repositories at once, a script for our mass-pr tool is available. If the plugin or the theme you’re working on changes a basic functionality of Discourse on purpose, then it’s possible to skip some of the examples from the core features specs: it_behaves_like "having working core features", skip_examples: %i[login likes] Here’s the complete list of keywords for skipping examples: login likes profile topics topics:read topics:reply topics:create search search:quick_search search:full_page

[imagen] loic: If the plugin or the theme you’re working on changes a basic functionality of Discourse on purpose, then it’s possible to skip some of the examples from the core features specs: it_behaves_like "having working core features", skip_examples: %i[login likes] Here’s the complete list of keywords for skipping examples: login likes profile topics topics:read topics:reply topics:create search search:quick_search search:full_page IMHO, it would be very handy and helpful to include this detail in spec/system/core_features_spec.rb main # frozen_string_literal: true # Parts of the core features examples can be skipped like so: # it_behaves_like "having working core features", skip_examples: %i[login likes] # # List of keywords for skipping examples: # login, likes, profile, topics, topics:read, topics:reply, topics:create, and spec/system/core_features_spec.rb cf5004661 # frozen_string_literal: true RSpec.describe "Core features", type: :system do before { upload_theme_or_component } it_behaves_like "having working core features" end … or the link of this topic :slight_smile:

That’s a good idea, it’s been done in DEV: Add short explanations for the core features specs by Flink · Pull Request #52 · discourse/discourse-theme-skeleton · GitHub and DEV: Add short explanations for the core features specs by Flink · Pull Request #78 · discourse/discourse-plugin-skeleton · GitHub :grin:

If your theme needs to have a different Theme authorized extensions all tests fail because the theme can’t load.

I recently stumbled on this issue. Here’s how the required extensions can be set: RSpec.describe "Core features" do + SiteSetting.theme_authorized_extensions = "js|css" before { upload_theme_or_component } it_behaves_like "having working core features" end

That’s not hard. I wonder what theme I was working on or if I solved the problem! :person_shrugging:

Nuevas especificaciones del sistema de funciones principales en plugins y temas

Desarrollador

pfaffman (Jay Pfaffman) 1 Agosto, 2026 16:30 6

Eso no es difícil. Me pregunto en qué tema estaba trabajando o si ¡resolví el problema!

Tema		Respuestas	Vistas
Plugin system tests failing Development	0	116	28 Enero 2026
End-to-end system testing for themes and theme components Developer Guides how-to , theme-guides	1	1383	2 Enero 2025
Write end-to-end system specs for the Discourse user interface Developer Guides	3	827	28 Agosto 2025
Developer Guides Index Developer Guides index	0	2481	15 Mayo 2024
DiscourseSkill.md Development	3	208	22 Septiembre 2026

Nuevas especificaciones del sistema de funciones principales en plugins y temas

Temas relacionados