From 8a103504e2b4d31db0a6a739b828b0634187437c Mon Sep 17 00:00:00 2001 From: Paul Gschwendtner Date: Tue, 3 Sep 2019 23:28:40 +0200 Subject: [PATCH] build: do not include material prebuilt theme twice in legacy tests Apparently we include the Angular Material prebuilt theme twice in the legacy Karma tests. This is because we also generate a second folder called `esm5` in the package output (for later use in the release composing step). This folder also contains the prebuilt themes as a side-effect of copying the assets for esm5 inlining/bundling. In any case, we should not import the theme using a glob, but rather use an explicit path (similar to how we do it for the mdc theme). --- test/karma.conf.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/karma.conf.js b/test/karma.conf.js index 72ce16d80999..66bf8a23b0dd 100644 --- a/test/karma.conf.js +++ b/test/karma.conf.js @@ -58,7 +58,7 @@ module.exports = config => { // Include a Material theme in the test suite. Also include the MDC theme as // karma runs tests for the MDC prototype components as well. { - pattern: 'dist/packages/**/core/theming/prebuilt/indigo-pink.css', + pattern: 'dist/packages/material/core/theming/prebuilt/indigo-pink.css', included: true, watched: true },