Skip to content

Commit b86bf06

Browse files
committed
add karma-spec-reporter to log info about skipped specs
- so that the CI logs show which tests were skipped - use with 'dots' reporter when not targeting an individual suite for cleaner output.
1 parent 8d7171f commit b86bf06

File tree

2 files changed

+11
-1
lines changed

2 files changed

+11
-1
lines changed

package.json

+1
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,7 @@
120120
"karma-firefox-launcher": "^1.0.0",
121121
"karma-jasmine": "^1.1.0",
122122
"karma-jasmine-spec-tags": "^1.0.1",
123+
"karma-spec-reporter": "0.0.30",
123124
"karma-verbose-reporter": "0.0.6",
124125
"madge": "^1.6.0",
125126
"node-sass": "^4.5.0",

test/jasmine/karma.conf.js

+10-1
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ func.defaultConfig = {
7777
// See note in CONTRIBUTING.md about more verbose reporting via karma-verbose-reporter:
7878
// https://www.npmjs.com/package/karma-verbose-reporter ('verbose')
7979
//
80-
reporters: ['progress'],
80+
reporters: isSingleSuiteRun ? ['progress'] : ['dots', 'spec'],
8181

8282
// web server port
8383
port: 9876,
@@ -119,6 +119,7 @@ func.defaultConfig = {
119119
extensions: ['.js'],
120120
watch: !isCI,
121121
debug: true
122+
},
122123

123124
// unfortunately a few tests don't behave well on CI
124125
// using `karma-jasmine-spec-tags`
@@ -128,6 +129,14 @@ func.defaultConfig = {
128129
skipTags: isCI ? 'noCI' : null
129130
},
130131

132+
// use 'karma-spec-reporter' to log info about skipped specs
133+
specReporter: {
134+
suppressErrorSummary: true,
135+
suppressFailed: true,
136+
suppressPassed: true,
137+
suppressSkipped: false,
138+
showSpecTiming: false,
139+
failFast: false
131140
}
132141
};
133142

0 commit comments

Comments
 (0)