Contents

@masking
Feature: The Reek API maintains backwards compatibility
  In order to use Reek without fuss
  As a developer
  I want to have a stable API

  Scenario: the demo example reports as expected
    When I run reek spec/samples/demo
    Then the exit status indicates smells
    And it reports:
      """
      spec/samples/demo/demo.rb -- 10 warnings:
        Dirty has no descriptive comment (IrresponsibleModule)
        Dirty#awful has 4 parameters (LongParameterList)
        Dirty#awful has boolean parameter 'log' (BooleanParameter)
        Dirty#awful has the parameter name 'x' (UncommunicativeParameterName)
        Dirty#awful has the parameter name 'y' (UncommunicativeParameterName)
        Dirty#awful has the variable name 'w' (UncommunicativeVariableName)
        Dirty#awful has unused parameter 'log' (UnusedParameters)
        Dirty#awful has unused parameter 'offset' (UnusedParameters)
        Dirty#awful has unused parameter 'x' (UnusedParameters)
        Dirty#awful has unused parameter 'y' (UnusedParameters)

      """

Version data entries

3 entries across 3 versions & 1 rubygems

Version	Path
reek-1.3.2	features/ruby_api/api.feature
reek-1.3.1	features/ruby_api/api.feature
reek-1.3	features/ruby_api/api.feature