Discource-C
/
discourse
mirror of https://github.com/discourse/discourse.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
discourse/app/views/qunit/theme.html.erb

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

54 lines
1.8 KiB
Plaintext
Raw Normal View History

FEATURE: Allow theme tests to be run in production (take 2) (#12845) This commit allows site admins to run theme tests in production via a new `/theme-qunit` route. When you visit `/theme-qunit`, you'll see a list of the themes/components installed on your site that have tests, and from there you can select a theme or component that you run its tests. We also have a new rake task `themes:install_and_test` that can be used to install a list of themes/components on a temporary database and run the tests of the themes/components that are installed. This rake task can be useful when upgrading/deploying a Discourse instance to make sure that the installed themes/components are compatible with the new Discourse version being deployed, and if the tests fail you can abort the build/deploy process so you don't end up with a broken site.
2021-04-28 16:12:08 -04:00
<!DOCTYPE html>
<html>
<head>
<title>Theme QUnit Test Runner</title>
<%= discourse_color_scheme_stylesheets %>
<%- if !@suggested_themes %>
Code review comments.
2021-06-17 22:16:26 -04:00
<%= discourse_stylesheet_link_tag(:desktop, theme_id: nil) %>
<%= discourse_stylesheet_link_tag(:test_helper, theme_id: nil) %>
DEV: Support for running theme test with Ember CLI (third attempt) The second attempt fixed issues with smoke test. This one makes sure minification only happens in production mode.
2022-01-13 15:16:34 -05:00
<%= preload_script "locales/#{I18n.locale}" %>
DEV: Remove ember-cli flags from the backend (#17147) …and other auxiliary code * Restore `QUNIT_EMBER_CLI` flag warning * Add `ALLOW_EMBER_CLI_PROXY_BYPASS`
2022-06-20 10:33:05 -04:00
<%= preload_script "vendor" %>
<%= preload_script "discourse" %>
FEATURE: Allow theme tests to be run in production (take 2) (#12845) This commit allows site admins to run theme tests in production via a new `/theme-qunit` route. When you visit `/theme-qunit`, you'll see a list of the themes/components installed on your site that have tests, and from there you can select a theme or component that you run its tests. We also have a new rake task `themes:install_and_test` that can be used to install a list of themes/components on a temporary database and run the tests of the themes/components that are installed. This rake task can be useful when upgrading/deploying a Discourse instance to make sure that the installed themes/components are compatible with the new Discourse version being deployed, and if the tests fail you can abort the build/deploy process so you don't end up with a broken site.
2021-04-28 16:12:08 -04:00
<%= preload_script "admin" %>
DEV: Support for running theme test with Ember CLI (third attempt) The second attempt fixed issues with smoke test. This one makes sure minification only happens in production mode.
2022-01-13 15:16:34 -05:00
<%= preload_script "discourse/tests/active-plugins" %>
FIX: When using Ember CLI, plugin admin code was not being loaded in tests (#16239)
2022-03-21 15:46:41 -04:00
<%= preload_script "admin-plugins" %>
DEV: Remove ember-cli flags from the backend (#17147) …and other auxiliary code * Restore `QUNIT_EMBER_CLI` flag warning * Add `ALLOW_EMBER_CLI_PROXY_BYPASS`
2022-06-20 10:33:05 -04:00
<%= preload_script "test-support" %>
<%= preload_script "test-helpers" %>
FEATURE: Allow theme tests to be run in production (take 2) (#12845) This commit allows site admins to run theme tests in production via a new `/theme-qunit` route. When you visit `/theme-qunit`, you'll see a list of the themes/components installed on your site that have tests, and from there you can select a theme or component that you run its tests. We also have a new rake task `themes:install_and_test` that can be used to install a list of themes/components on a temporary database and run the tests of the themes/components that are installed. This rake task can be useful when upgrading/deploying a Discourse instance to make sure that the installed themes/components are compatible with the new Discourse version being deployed, and if the tests fail you can abort the build/deploy process so you don't end up with a broken site.
2021-04-28 16:12:08 -04:00
<%= theme_translations_lookup %>
<%= theme_js_lookup %>
<%= theme_lookup("head_tag") %>
<%= theme_tests %>
<%= tag.meta id: 'data-discourse-setup', data: client_side_setup_data %>
<meta property="og:title" content="">
<meta property="og:url" content="">
DEV: Support for running theme test with Ember CLI (third attempt) The second attempt fixed issues with smoke test. This one makes sure minification only happens in production mode.
2022-01-13 15:16:34 -05:00
<meta name="discourse/config/environment" content="<%=u discourse_config_environment(testing: true) %>" />
FEATURE: Allow theme tests to be run in production (take 2) (#12845) This commit allows site admins to run theme tests in production via a new `/theme-qunit` route. When you visit `/theme-qunit`, you'll see a list of the themes/components installed on your site that have tests, and from there you can select a theme or component that you run its tests. We also have a new rake task `themes:install_and_test` that can be used to install a list of themes/components on a temporary database and run the tests of the themes/components that are installed. This rake task can be useful when upgrading/deploying a Discourse instance to make sure that the installed themes/components are compatible with the new Discourse version being deployed, and if the tests fail you can abort the build/deploy process so you don't end up with a broken site.
2021-04-28 16:12:08 -04:00
<%- else %>
<style>
html {
font-family: Arial;
}
</style>
<%- end %>
DEV: Allow running theme-qunit tests via testem (#16540) This allows `QUNIT_EMBER_CLI=1 bin/rake theme:qunit[...]` to test themes using `testem` with Ember-CLI-generated assets
2022-04-22 10:04:01 -04:00
<%- if params['testem'] %>
FIX: Defer scripts on theme-tests route (#17171) Small follow-up to #17063. That PR broke the theme tests route locally. This PR fixes that.
2022-06-21 00:44:31 -04:00
<script defer src="/assets/testem.js"></script>
DEV: Allow running theme-qunit tests via testem (#16540) This allows `QUNIT_EMBER_CLI=1 bin/rake theme:qunit[...]` to test themes using `testem` with Ember-CLI-generated assets
2022-04-22 10:04:01 -04:00
<%- end %>
FEATURE: Allow theme tests to be run in production (take 2) (#12845) This commit allows site admins to run theme tests in production via a new `/theme-qunit` route. When you visit `/theme-qunit`, you'll see a list of the themes/components installed on your site that have tests, and from there you can select a theme or component that you run its tests. We also have a new rake task `themes:install_and_test` that can be used to install a list of themes/components on a temporary database and run the tests of the themes/components that are installed. This rake task can be useful when upgrading/deploying a Discourse instance to make sure that the installed themes/components are compatible with the new Discourse version being deployed, and if the tests fail you can abort the build/deploy process so you don't end up with a broken site.
2021-04-28 16:12:08 -04:00
</head>
<body>
DEV: Remove ember-cli flags from the backend (#17147) …and other auxiliary code * Restore `QUNIT_EMBER_CLI` flag warning * Add `ALLOW_EMBER_CLI_PROXY_BYPASS`
2022-06-20 10:33:05 -04:00
<%- if @suggested_themes %>
DEV: Minor changes to `/theme-qunit` landing page (#13032)
2021-05-11 10:45:07 -04:00
<h2>Theme QUnit Test Runner</h2>
<%- if @suggested_themes.size == 0 %>
<p>Cannot find any theme tests.</p>
<%- else %>
<h3>Select a theme/component: </h3>
<%- @suggested_themes.each do |(id, name)| %>
DEV: Use path instead of absolute URL for theme test links (#17172) In development, this avoids the surprising switch from ember-cli to rails
2022-06-21 06:32:46 -04:00
<h4><%= link_to name, theme_qunit_path(id: id) %></h4>
DEV: Minor changes to `/theme-qunit` landing page (#13032)
2021-05-11 10:45:07 -04:00
<%- end %>
FEATURE: Allow theme tests to be run in production (take 2) (#12845) This commit allows site admins to run theme tests in production via a new `/theme-qunit` route. When you visit `/theme-qunit`, you'll see a list of the themes/components installed on your site that have tests, and from there you can select a theme or component that you run its tests. We also have a new rake task `themes:install_and_test` that can be used to install a list of themes/components on a temporary database and run the tests of the themes/components that are installed. This rake task can be useful when upgrading/deploying a Discourse instance to make sure that the installed themes/components are compatible with the new Discourse version being deployed, and if the tests fail you can abort the build/deploy process so you don't end up with a broken site.
2021-04-28 16:12:08 -04:00
<%- end %>
<%- end %>
</body>
DEV: Support for running theme test with Ember CLI (third attempt) The second attempt fixed issues with smoke test. This one makes sure minification only happens in production mode.
2022-01-13 15:16:34 -05:00
<%- if !@suggested_themes %>
DEV: Remove ember-cli flags from the backend (#17147) …and other auxiliary code * Restore `QUNIT_EMBER_CLI` flag warning * Add `ALLOW_EMBER_CLI_PROXY_BYPASS`
2022-06-20 10:33:05 -04:00
<%= preload_script "scripts/discourse-test-listen-boot" %>
<%= preload_script "scripts/discourse-boot" %>
DEV: Support for running theme test with Ember CLI (third attempt) The second attempt fixed issues with smoke test. This one makes sure minification only happens in production mode.
2022-01-13 15:16:34 -05:00
<%- end %>
FEATURE: Allow theme tests to be run in production (take 2) (#12845) This commit allows site admins to run theme tests in production via a new `/theme-qunit` route. When you visit `/theme-qunit`, you'll see a list of the themes/components installed on your site that have tests, and from there you can select a theme or component that you run its tests. We also have a new rake task `themes:install_and_test` that can be used to install a list of themes/components on a temporary database and run the tests of the themes/components that are installed. This rake task can be useful when upgrading/deploying a Discourse instance to make sure that the installed themes/components are compatible with the new Discourse version being deployed, and if the tests fail you can abort the build/deploy process so you don't end up with a broken site.
2021-04-28 16:12:08 -04:00
</html>