diff options
author | winniehell <git@winniehell.de> | 2016-07-01 17:29:25 +0200 |
---|---|---|
committer | winniehell <git@winniehell.de> | 2016-08-07 21:52:37 +0200 |
commit | 5e1ac6275ffa292fe7f6b8b5b74d92b99385d7d5 (patch) | |
tree | 1cfc3301714800fc89ae2fb0e8ed077d441b84cf /spec/teaspoon_env.rb | |
parent | 91030230545a199a86c2742600a7a2e68ef75c98 (diff) | |
download | gitlab-ce-5e1ac6275ffa292fe7f6b8b5b74d92b99385d7d5.tar.gz |
Add test coverage analysis for CoffeeScript (!5052)
Diffstat (limited to 'spec/teaspoon_env.rb')
-rw-r--r-- | spec/teaspoon_env.rb | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/spec/teaspoon_env.rb b/spec/teaspoon_env.rb index 1a3bbb9c8cc..5ea020f313c 100644 --- a/spec/teaspoon_env.rb +++ b/spec/teaspoon_env.rb @@ -149,7 +149,7 @@ Teaspoon.configure do |config| # Specify that you always want a coverage configuration to be used. Otherwise, specify that you want coverage # on the CLI. # Set this to "true" or the name of your coverage config. - # config.use_coverage = nil + config.use_coverage = true # You can have multiple coverage configs by passing a name to config.coverage. # e.g. config.coverage :ci do |coverage| @@ -158,15 +158,15 @@ Teaspoon.configure do |config| # Which coverage reports Istanbul should generate. Correlates directly to what Istanbul supports. # # Available: text-summary, text, html, lcov, lcovonly, cobertura, teamcity - # coverage.reports = ["text-summary", "html"] + coverage.reports = ["text-summary", "html"] # The path that the coverage should be written to - when there's an artifact to write to disk. # Note: Relative to `config.root`. - # coverage.output_path = "coverage" + coverage.output_path = "coverage-javascript" # Assets to be ignored when generating coverage reports. Accepts an array of filenames or regular expressions. The # default excludes assets from vendor, gems and support libraries. - # coverage.ignore = [%r{/lib/ruby/gems/}, %r{/vendor/assets/}, %r{/support/}, %r{/(.+)_helper.}] + coverage.ignore = [%r{vendor/}, %r{spec/}] # Various thresholds requirements can be defined, and those thresholds will be checked at the end of a run. If any # aren't met the run will fail with a message. Thresholds can be defined as a percentage (0-100), or nil. |