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 …

[image] 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 lis…

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 · GitH…

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

New core features system specs in plugins and themes

Development

pfaffman (Jay Pfaffman) August 1, 2026, 4:30pm 6

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

Topic		Replies	Views
Plugin system tests failing Development	0	73	January 28, 2026
End-to-end system testing for themes and theme components Developer Guides how-to , theme-guides	1	1219	January 2, 2025
Write end-to-end system specs for the Discourse user interface Developer Guides	3	669	August 28, 2025
Developer Guides Index Developer Guides index	0	2098	May 15, 2024
I propose a feature that allows users to update only themes and components Feature	1	90	March 23, 2026

New core features system specs in plugins and themes

Related topics