Sha256: db96971650111a172db5d2aaf9794990660a19a098af27bd7a98ea56966eee57
Contents?: true
Size: 1.08 KB
Versions: 13
Compression:
Stored size: 1.08 KB
Contents
Feature: detects code smells
In order to find code smells
As a ruby developer
I want to run warder with --code-smells option
Scenario: run warder with enabled code smells option
Given I have valid file in directory
When I run `warder --code-smells`
Then warder detects code smells issues
Then the exit status should be 0
Scenario: run warder with enabled code smells option on invalid file
Given I have invalid_code_smells file in directory
When I run `warder --code-smells`
Then warder detects code smells issues
Then the exit status should be 1
Scenario: run warder with enabled code smells option on valid file only
Given I have valid file in directory
And I have invalid_code_smells file in directory
When I run `warder --code-smells valid.rb`
Then warder does nothing
Then the exit status should be 0
Scenario: run warder with disabled code smells option on invalid file
Given I have invalid_code_smells file in directory
When I run `warder --no-code-smells`
Then warder does nothing
Then the exit status should be 0
Version data entries
13 entries across 13 versions & 1 rubygems