chutney 3.0.0.beta.1 → 3.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3eb2bbfa506f0fde529c0365064ffe21e6f102e37d3790e138e09c972c07319d
-  data.tar.gz: 8951672afdbf61863d949ebce24862f203395a931228bd98a0fe1d401ad1544f
+  metadata.gz: f9a4331eb00fea09babefa186ea7d1e51f13bacbd56cf381cf3fb3d58f293346
+  data.tar.gz: 16b169146ac5034d46eee9d6858a6b219d854b00d71445a5baca5d6532340b4a
 SHA512:
-  metadata.gz: d41e8f3694940cb023fd03192b973a3778366e2745b544e8003f8d2f02c65285de6c7e9b8e254e89ce714732474c0837db8487da0eefbaba77ed405a02cf4f57
-  data.tar.gz: 1a3f433eb45190171bad88ca533e65f533f59ff5d2c2654a3da41b4f585b3abab3a6814824b0925ea0973ba76e331ce2bb9ab9345cd2f73ae1d242f64641eaff
+  metadata.gz: 2a8000d183486b9c3201ff22e43fbcfc316d5117b68539aae88b0d22ec2d9d549fdd945c8a4a15393f14d147e53c038923be3aa1dda3483a6066fb58a48ff50f
+  data.tar.gz: a9a32669fb7ddfd30e742647883a079b654e570b2e6653996a8c9ea26fe1601a402148aabf357e6a79f9150d9f747c8ce6fc80b8036180e3a5b53b3096930950

data/.github/dependabot.yml

@@ -0,0 +1,16 @@
+version: 2
+updates:
+- package-ecosystem: bundler
+  directory: "/"
+  schedule:
+    interval: daily
+  open-pull-requests-limit: 10
+  ignore:
+  - dependency-name: rubocop
+    versions:
+    - 1.10.0
+    - 1.11.0
+    - 1.12.0
+    - 1.12.1
+    - 1.9.0
+    - 1.9.1

data/.rubocop.yml

@@ -25,7 +25,8 @@ Layout/LineLength:
 # Offense count: 1
 # Configuration parameters: CountComments.
 Metrics/MethodLength:
-  Max: 11
+  Max: 20
+
 
 # Offense count: 1
 # Cop supports --auto-correct.
@@ -52,11 +53,11 @@ Layout/HeredocIndentation:
     - "**/*_spec.rb"
 
 Layout/TrailingWhitespace:
-  Enabled: false
+  Enabled: true
 
 Style/FrozenStringLiteralComment:
   Enabled: true
-  
+
 Style/StringConcatenation:
   Enabled: false
 

data/LICENSE.txt

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2015 Funkwerk AG
+Copyright (c) 2020, 2021 Nigel Brookes-Thomas
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/README.md

@@ -19,4 +19,10 @@
 
 </div>
 
-Read the documentation [here](https://billyruffian.github.io/chutney/).
+Read the documentation [here](https://billyruffian.github.io/chutney/) or try [Chutney Online](https://chutney.billy-ruffian.co.uk).
+
+See [this page](https://billyruffian.github.io/chutney/usage/rules.html) for a full list of the rules chutney encourages.
+
+## Notes
+
+Chutney 3+ has replaced its direct dependency on Cucumber and instead uses the excellent [cuke_modeller](https://github.com/enkessler/cuke_modeler) to parse your feature files. 

data/Rakefile

@@ -18,14 +18,12 @@ end
 
 desc 'Checks ruby style'
 task :rubocop do
-  begin
-    sh 'rubocop -a'
-  rescue RuntimeError => e
-    # Rubocop failing due to style violations is fine. Other errors should bubble up to our attention.
-    raise e unless e.message =~ /status \(1\).*rubocop/
-
-    puts 'Rubocop failed'
-  end
+  sh 'rubocop -a'
+rescue RuntimeError => e
+  # Rubocop failing due to style violations is fine. Other errors should bubble up to our attention.
+  raise e unless e.message =~ /status \(1\).*rubocop/
+
+  puts 'Rubocop failed'
 end
 
 task :spec do

data/chutney.gemspec

@@ -15,8 +15,12 @@ Gem::Specification.new do |spec|
   spec.email       = ['nigel@brookes-thomas.co.uk']
 
   spec.summary     = 'A linter for multi-lingual Gherkin'
-  spec.description = 'A linter for your Cucumber features. '  \
-                      'It supports any spoken language Cucumber supports.'
+  spec.description = 'A linter for your Cucumber features. '                    \
+                     'Making sure you have nice, expressible Gherkin is '       \
+                     'essential is making sure you have a readable test-base. ' \
+                     'Chutney is designed to sniff out smells in your feature ' \
+                     'files. '                                                  \
+                     'It supports any spoken language Cucumber supports.'
 
   spec.homepage    = 'https://billyruffian.github.io/chutney/'
   spec.license     = 'MIT'
@@ -46,20 +50,19 @@ Gem::Specification.new do |spec|
   
   spec.add_runtime_dependency 'amatch', '~> 0.4.0'
   spec.add_runtime_dependency 'cuke_modeler', '~> 3.3'
-  spec.add_runtime_dependency 'gherkin', '>= 5.1.0', '< 9.1'
   spec.add_runtime_dependency 'i18n', '~> 1.8.2'
   spec.add_runtime_dependency 'pastel', '~> 0.7'
   spec.add_runtime_dependency 'tty-pie', '~> 0.3'
 
 
   spec.add_development_dependency 'coveralls', '~> 0.8'
-  spec.add_development_dependency 'cucumber', '~> 5.1'
+  spec.add_development_dependency 'cucumber', '~> 6.0'
   spec.add_development_dependency 'pry-byebug', '~> 3.0'
   spec.add_development_dependency 'rake', '~> 13.0'
   spec.add_development_dependency 'rerun', '~> 0.13'
   spec.add_development_dependency 'rspec-expectations', '~> 3.0'
-  spec.add_development_dependency 'rubocop', '~> 0.89.0'
+  spec.add_development_dependency 'rubocop', '~> 1.14.0'
   spec.add_development_dependency 'rspec', '~> 3.8'
   
-  spec.required_ruby_version = '~> 2.6'
+  spec.required_ruby_version = '>= 2.6'
 end

data/config/{chutney.yml → chutney_defaults.yml}

@@ -36,6 +36,8 @@ InvalidStepFlow:
     Enabled: true
 RequiredTagsStartsWith:
     Enabled: false
+SameTagDifferentCase:
+    Enabled: true
 SameTagForAllScenarios:
     Enabled: true
 ScenarioNamesMatch:

data/docs/index.md

@@ -18,4 +18,4 @@ You're trying to follow TDD or ATDD principles, you're writing executable specif
 
 Cucumber itself is an awesome tool which bridges with gap between business language, software development language and the language of testers. With all these folks interested, it's easy to write problematic and hard to maintain features. Chutney tries to help with that by having a common set of quality rules for your feature files.
 
-Chutney is able to lint feature files in any spoken language supported by Cucumber 3.
+Chutney is able to lint feature files in any spoken language supported by Cucumber.

data/docs/usage/rules.md

@@ -9,98 +9,68 @@ nav_order: 2
 
 Chutney enforces its rules with the linters. These are:
 
-[AvoidFullStop](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_full_stop.feature)
-: Don't have a full stop (period) at the end of step because it makes step reuse really hard.
+[AvoidFullStop](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_full_stop.feature): Don't have a full stop (period) at the end of step because it makes step reuse really hard.
 
-[AvoidOutlineForSingleExample](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_outline_for_single_example.feature)
-: If you only have a single example in your example table, use a plain-old scenario instead.
+[AvoidOutlineForSingleExample](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_outline_for_single_example.feature): If you only have a single example in your example table, use a plain-old scenario instead.
 
-[AvoidScripting](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_scripting.feature)
-: You have a lot of steps, are you sure you're not scripting the scenario when you should be specifying the behaviour of the system?
+[AvoidScripting](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_scripting.feature): You have a lot of steps, are you sure you're not scripting the scenario when you should be specifying the behaviour of the system?
 
-[AvoidTypographersQuotes](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_typographers_quotes.feature)
-: Cutting and pasting from Word documents? Is that pasting in curly-quotes instead of neutral ones you would type on a keyboard? Are you sure that's what you want?
+[AvoidTypographersQuotes](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_typographers_quotes.feature): Cutting and pasting from Word documents? Is that pasting in curly-quotes instead of neutral ones you would type on a keyboard? Are you sure that's what you want?
 
-[BackgroundDoesMoreThanSetup](https://github.com/BillyRuffian/chutney/blob/master/features/background_does_more_than_setup.feature)
-: Background in feature files should only do setup activity and so they should only contain `Given` steps.
+[BackgroundDoesMoreThanSetup](https://github.com/BillyRuffian/chutney/blob/master/features/background_does_more_than_setup.feature): Background in feature files should only do setup activity and so they should only contain `Given` steps.
 
-[BackgroundRequiresMultipleScenarios](https://github.com/BillyRuffian/chutney/blob/master/features/background_requires_multiple_scenarios.feature)
-: If you only have one scenario, don't bother having a Background section.
+[BackgroundRequiresMultipleScenarios](https://github.com/BillyRuffian/chutney/blob/master/features/background_requires_multiple_scenarios.feature): If you only have one scenario, don't bother having a Background section.
 
-[BadScenarioName](https://github.com/BillyRuffian/chutney/blob/master/features/bad_scenario_name.feature)
-: You should avoid using words like 'test' or 'check' in your scenario names, instead you should define the behaviour of your system.
+[BadScenarioName](https://github.com/BillyRuffian/chutney/blob/master/features/bad_scenario_name.feature): You should avoid using words like 'test' or 'check' in your scenario names, instead you should define the behaviour of your system.
 
-[EmptyFeatureFile](https://github.com/BillyRuffian/chutney/blob/master/features/empty_feature_file.feature)
-: The feature should have content and should avoid committing empty features to repositories.
+[EmptyFeatureFile](https://github.com/BillyRuffian/chutney/blob/master/features/empty_feature_file.feature): The feature should have content and should avoid committing empty features to repositories.
 
-[FileNameDiffersFeatureName](https://github.com/BillyRuffian/chutney/blob/master/features/file_name_differs_feature_name.feature)
-: The feature should have a name that follows the file name.
+[FileNameDiffersFeatureName](https://github.com/BillyRuffian/chutney/blob/master/features/file_name_differs_feature_name.feature): The feature should have a name that follows the file name.
 
-[GivensAfterBackground](https://github.com/BillyRuffian/chutney/blob/master/features/givens_after_background.feature)
-: If you have a Background section and your scenario needs more preconditions then it should start immediately with an `And` step and not another `Given`.
+[GivensAfterBackground](https://github.com/BillyRuffian/chutney/blob/master/features/givens_after_background.feature): If you have a Background section and your scenario needs more preconditions then it should start immediately with an `And` step and not another `Given`.
 
-[InvalidFileName](https://github.com/BillyRuffian/chutney/blob/master/features/invalid_file_name.feature)
-: Make sure your file name is in snake case, not mixed case or with spaces.
+[InvalidFileName](https://github.com/BillyRuffian/chutney/blob/master/features/invalid_file_name.feature): Make sure your file name is in snake case, not mixed case or with spaces.
 
-[InvalidStepFlow](https://github.com/BillyRuffian/chutney/blob/master/features/invalid_step_flow.feature)
-: Your scenarios should follow Given → When → Then, in that order.
+[InvalidStepFlow](https://github.com/BillyRuffian/chutney/blob/master/features/invalid_step_flow.feature): Your scenarios should follow Given → When → Then, in that order.
 
-[MissingExampleName](https://github.com/BillyRuffian/chutney/blob/master/features/missing_example_name.feature)
-: If you have more than one example table in your scenario, they should each be given unique names.
+[MissingExampleName](https://github.com/BillyRuffian/chutney/blob/master/features/missing_example_name.feature): If you have more than one example table in your scenario, they should each be given unique names.
 
-[MissingFeatureDescription](https://github.com/BillyRuffian/chutney/blob/master/features/missing_feature_description.feature)
-: Your feature should have a value statement. These are usually in the form 'As a... I want.. So that...'.
+[MissingFeatureDescription](https://github.com/BillyRuffian/chutney/blob/master/features/missing_feature_description.feature): Your feature should have a value statement. These are usually in the form 'As a... I want.. So that...'.
 
-[MissingFeatureName](https://github.com/BillyRuffian/chutney/blob/master/features/missing_feature_name.feature)
-: You should give your features a descriptive name.
+[MissingFeatureName](https://github.com/BillyRuffian/chutney/blob/master/features/missing_feature_name.feature): You should give your features a descriptive name.
 
-[MissingScenarioName](https://github.com/BillyRuffian/chutney/blob/master/features/missing_scenario_name.feature)
-: You should name your scenarios and scenario outlines.
+[MissingScenarioName](https://github.com/BillyRuffian/chutney/blob/master/features/missing_scenario_name.feature): You should name your scenarios and scenario outlines.
 
-[MissingTestAction](https://github.com/BillyRuffian/chutney/blob/master/features/missing_test_action.feature)
-: You don't have an action (a `When` step) in your scenario.
+[MissingTestAction](https://github.com/BillyRuffian/chutney/blob/master/features/missing_test_action.feature): You don't have an action (a `When` step) in your scenario.
 
-[MissingVerification](https://github.com/BillyRuffian/chutney/blob/master/features/missing_verification.feature)
-: You don't have a verification step (a `Then` step) in your scenario.
+[MissingVerification](https://github.com/BillyRuffian/chutney/blob/master/features/missing_verification.feature): You don't have a verification step (a `Then` step) in your scenario.
 
-[RequiredTagsStartWith](https://github.com/BillyRuffian/chutney/blob/master/features/required_tags_starts_with.feature)
-: Chutney can enforce a configurable naming prefix for your tags.
+[RequiredTagsStartWith](https://github.com/BillyRuffian/chutney/blob/master/features/required_tags_starts_with.feature): Chutney can enforce a configurable naming prefix for your tags.
 
-[SameTagForAllScenarios](https://github.com/BillyRuffian/chutney/blob/master/features/same_tag_for_all_scenarios.feature)
-: You have the same tag for all you scenarios; move the tag to the feature level instead.
+[SameTagForDifferentCase](https://github.com/BillyRuffian/chutney/blob/master/features/same_tag_different_case.feature): Don't mix the case of tags which have already appeared. Cucumber tags are case sensitive. *Since 3.1.0*
 
-[ScenarioNamesMatch](https://github.com/BillyRuffian/chutney/blob/master/features/scenario_names_match.feature)
-: Chutney can enforce a naming convention for your scenario names.
+[SameTagForAllScenarios](https://github.com/BillyRuffian/chutney/blob/master/features/same_tag_for_all_scenarios.feature): You have the same tag for all you scenarios; move the tag to the feature level instead.
 
-[TagUsedMultipleTimes](https://github.com/BillyRuffian/chutney/blob/master/features/tag_used_multiple_times.feature)
-: Chutney can warn if you have used a tag a lot with a feature.
+[ScenarioNamesMatch](https://github.com/BillyRuffian/chutney/blob/master/features/scenario_names_match.feature): Chutney can enforce a naming convention for your scenario names.
 
-[TooClumsy](https://github.com/BillyRuffian/chutney/blob/master/features/too_clumsy.feature)
-: This is a very long scenario. Consider writing it more concisely.
+[TagUsedMultipleTimes](https://github.com/BillyRuffian/chutney/blob/master/features/tag_used_multiple_times.feature): Chutney can warn if you have used a tag a lot with a feature.
 
-[TooLongStep](https://github.com/BillyRuffian/chutney/blob/master/features/too_long_step.feature)
-: This is a very long step. Consider writing it more concisely.
+[TooClumsy](https://github.com/BillyRuffian/chutney/blob/master/features/too_clumsy.feature): This is a very long scenario. Consider writing it more concisely.
 
-[TooManyDifferentTags](https://github.com/BillyRuffian/chutney/blob/master/features/too_many_different_tags.feature)
-: This feature has a lot of different tags.
+[TooLongStep](https://github.com/BillyRuffian/chutney/blob/master/features/too_long_step.feature): This is a very long step. Consider writing it more concisely.
 
-[TooManySteps](https://github.com/BillyRuffian/chutney/blob/master/features/too_many_steps.feature)
-: This feature has a lot of steps. Consider writing it more concisely.
+[TooManyDifferentTags](https://github.com/BillyRuffian/chutney/blob/master/features/too_many_different_tags.feature): This feature has a lot of different tags.
 
-[TooManyTags](https://github.com/BillyRuffian/chutney/blob/master/features/too_many_tags.feature)
-: There are a lot of tags in this feature.
+[TooManySteps](https://github.com/BillyRuffian/chutney/blob/master/features/too_many_steps.feature): This feature has a lot of steps. Consider writing it more concisely.
 
-[UniqueScenarioNames](https://github.com/BillyRuffian/chutney/blob/master/features/unique_scenario_names.feature)
-: You have duplicated a scenario name when they should be unique.
+[TooManyTags](https://github.com/BillyRuffian/chutney/blob/master/features/too_many_tags.feature): There are a lot of tags in this feature.
 
-[UnknownVariable](https://github.com/BillyRuffian/chutney/blob/master/features/unknown_variable.feature)
-: You are referencing a variable which doesn't appear to be defined. This is a source of subtle errors.
+[UniqueScenarioNames](https://github.com/BillyRuffian/chutney/blob/master/features/unique_scenario_names.feature): You have duplicated a scenario name when they should be unique.
 
-[UnusedVariable](https://github.com/BillyRuffian/chutney/blob/master/features/unused_variable.feature)
-: You have a variable which you are not using.
+[UnknownVariable](https://github.com/BillyRuffian/chutney/blob/master/features/unknown_variable.feature): You are referencing a variable which doesn't appear to be defined. This is a source of subtle errors.
 
-[UseBackground](https://github.com/BillyRuffian/chutney/blob/master/features/use_background.feature)
-: You have a setup setup used in all of your scenarios. Move it to a Background section.
+[UnusedVariable](https://github.com/BillyRuffian/chutney/blob/master/features/unused_variable.feature): You have a variable which you are not using.
 
-[UseOutline](https://github.com/BillyRuffian/chutney/blob/master/features/use_outline.feature)
-: You have very similar scenarios. You should consider if they should be combined into a Scenario Outline.
+[UseBackground](https://github.com/BillyRuffian/chutney/blob/master/features/use_background.feature): You have a setup setup used in all of your scenarios. Move it to a Background section.
+
+[UseOutline](https://github.com/BillyRuffian/chutney/blob/master/features/use_outline.feature): You have very similar scenarios. You should consider if they should be combined into a Scenario Outline.

data/exe/chutney

@@ -12,19 +12,37 @@ formatters = Set.new
 
 OptionParser.new do |opts|
   opts.banner = 'Usage: chutney [files]'
-  opts.on('-f', 
-          '--format [formatter]', 
+  opts.on('-f',
+          '--format [formatter]',
           'One of JSONFormatter, PieFormatter or RainbowFormatter (default).') do |formatter|
     raise 'No Such Formatter' unless %w[JSONFormatter PieFormatter RainbowFormatter].include? formatter
 
     formatters << formatter
   end
+
+  opts.on('-l',
+          '--linters',
+          'List the linter status by this configuration and exit') do
+    pastel = Pastel.new
+    chutney_config = Chutney::ChutneyLint.new.configuration
+    max_name_length = chutney_config.keys.map(&:length).max + 1
+    chutney_config.each do |linter, value|
+      print pastel.cyan(linter.ljust(max_name_length))
+
+      if value['Enabled']
+        puts pastel.green('enabled')
+      else
+        puts pastel.red('disabled')
+      end
+    end
+    exit
+  end
 end.parse!
 
 formatters << 'RainbowFormatter' if formatters.empty?
 
 files = ARGV.map { |pattern| Dir.glob(pattern) }.flatten
-files = Dir.glob('features/**/*.feature') if ARGV.empty? 
+files = Dir.glob('features/**/*.feature') if ARGV.empty?
 
 linter = Chutney::ChutneyLint.new(*files)
 report = linter.analyse

data/lib/chutney.rb

@@ -23,6 +23,7 @@ require 'chutney/linter/missing_scenario_name'
 require 'chutney/linter/missing_test_action'
 require 'chutney/linter/missing_verification'
 require 'chutney/linter/required_tags_starts_with'
+require 'chutney/linter/same_tag_different_case'
 require 'chutney/linter/same_tag_for_all_scenarios'
 require 'chutney/linter/scenario_names_match'
 require 'chutney/linter/tag_used_multiple_times'
@@ -36,6 +37,7 @@ require 'chutney/linter/unknown_variable'
 require 'chutney/linter/unused_variable'
 require 'chutney/linter/use_background'
 require 'chutney/linter/use_outline'
+require 'chutney/version'
 
 require 'cuke_modeler'
 require 'forwardable'
@@ -58,14 +60,18 @@ module Chutney
       @files = files
       @results = Hash.new { |h, k| h[k] = [] }
       i18n_paths = Dir[File.expand_path(File.join(__dir__, 'config/locales')) + '/*.yml']
-      return if I18n.load_path.include?(i18n_paths)
 
-      I18n.load_path << i18n_paths
+      i18n_paths.each do |path|
+        next if I18n.load_path.include?(path)
+
+        I18n.load_path << path
+        I18n.backend.reload!
+      end
     end
 
     def configuration
       unless @config
-        default_file = [File.expand_path('..', __dir__), '**/config', 'chutney.yml']
+        default_file = [File.expand_path('..', __dir__), '**/config', 'chutney_defaults.yml']
         config_file = Dir.glob(File.join(default_file)).first.freeze
         @config = Configuration.new(config_file)
       end

data/lib/chutney/configuration.rb

@@ -1,7 +1,8 @@
 # frozen_string_literal: true
 
 require 'delegate'
-module Chutney 
+
+module Chutney
   # gherkin_lint configuration object
   class Configuration < SimpleDelegator
     def initialize(path)
@@ -20,7 +21,11 @@ module Chutney
     end
 
     def load_user_configuration
-      config_file = Dir.glob(File.join(Dir.pwd, '**', '.chutney.yml')).first
+      config_files = ['chutney.yml', '.chutney.yml'].map do |fname|
+        Dir.glob(File.join(Dir.pwd, '**', fname))
+      end.flatten
+
+      config_file = config_files.first
       merge_config(config_file) if !config_file.nil? && File.exist?(config_file)
     end
 

data/lib/chutney/formatter.rb

@@ -4,18 +4,17 @@ module Chutney
   # base class for all formatters
   class Formatter
     attr_accessor :results
-    
+
     def initialize
       @results = {}
-    end  
-        
+    end
+
     def files
       results.map { |k, _v| k }
     end
-    
+
     def files_with_issues
       results.filter { |_k, v| v.any? { |r| r[:issues].count.positive? } }
     end
-    
   end
 end

data/lib/chutney/formatter/pie_formatter.rb

@@ -6,10 +6,6 @@ require 'tty/pie'
 module Chutney
   # format results as pie charts
   class PieFormatter < Formatter
-    def initialize
-      super
-    end
-    
     def format
       data = top_offences.map do |offence|
         {
@@ -21,14 +17,14 @@ module Chutney
       end
       print_report(data)
     end
-    
+
     def print_report(data)
       return if data.empty?
 
       print TTY::Pie.new(data: data, radius: 8, legend: { format: '%<label>s %<name>s %<value>i' })
       puts
     end
-    
+
     def top_offences
       offence = Hash.new(0)
       files_with_issues.each do |_file, linter|
@@ -38,9 +34,9 @@ module Chutney
       end
       offence.reject { |_k, v| v.zero? }.sort_by { |_linter, count| -count }
     end
-    
+
     def char_loop
-      @char_looper ||= Fiber.new do 
+      @char_looper ||= Fiber.new do
         chars = %w[• x + @ * / -]
         current = 0
         loop do
@@ -51,10 +47,10 @@ module Chutney
       end
       @char_looper.resume
     end
-    
+
     def colour_loop
-      @colour_looper ||= Fiber.new do 
-        colours = %i[bright_cyan bright_magenta bright_yellow bright_green] 
+      @colour_looper ||= Fiber.new do
+        colours = %i[bright_cyan bright_magenta bright_yellow bright_green]
         current = 0
         loop do
           current = 0 if current >= colours.count
@@ -64,7 +60,7 @@ module Chutney
       end
       @colour_looper.resume
     end
-    
+
     def put_summary
       pastel = Pastel.new
       print "#{files.count} features inspected, "
@@ -74,6 +70,5 @@ module Chutney
         puts pastel.red("#{files_with_issues.count} taste nasty")
       end
     end
-    
   end
 end