Contents

Feature: The Reek CLI maintains backwards compatibility
  In order to use Reek without fuss
  As a developer
  I want to have a stable basic command line interface

  Scenario: the example from README reports as expected
    Given the smelly file 'smelly.rb'
    When I run reek smelly.rb
    Then the exit status indicates smells
    And it reports:
    """
    smelly.rb -- 2 warnings:
      [4]:UncommunicativeMethodName: Smelly#x has the name 'x'
      [5]:UncommunicativeVariableName: Smelly#x has the variable name 'y'
    """

Version data entries

21 entries across 19 versions & 2 rubygems

Version	Path
reek-4.8.2	features/command_line_interface/basic_usage.feature