warder 0.3.2 → 0.3.4

data/Gemfile

@@ -1,4 +0,0 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in warder.gemspec
-gemspec

data/LICENSE.txt

@@ -1,22 +0,0 @@
-Copyright (c) 2013 Yura Tolstik
-
-MIT License
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -1,130 +0,0 @@
-# Warder
-
-[![Build Status](https://travis-ci.org/yltsrc/warder.svg?branch=master)](https://travis-ci.org/yltsrc/warder)
-[![Code Climate](https://codeclimate.com/github/yltsrc/warder.svg)](https://codeclimate.com/github/yltsrc/warder)
-[![Dependency Status](https://gemnasium.com/yltsrc/warder.svg)](https://gemnasium.com/yltsrc/warder)
-
-## Getting started
-
-Main goal of this project was to provide you tool, which will help make code
-better. I used these tools for a while and can provide some tips.
-
-Just to start with warder, it would be great to do something simple.
-And I will recommend to start with checking your bundle for security issues
-
-    $ warder --bundle-audit
-
-Sooner or later you will start with code cleanup. There are two main ways to
-deal with it, depending what you plan to achieve. If you are interested in clean
-code, according to style guides, you may want to use
-
-    $ warder --style-guide
-
-But if you want to see you code OOP-friendly, then you need different approach
-
-    $ warder --code-smell
-
-Next steps for stylish code are:
-
-    $ warder --magick-numbers
-    $ warder --code-duplication
-
-And for OOP-style code next steps will be:
-
-    $ warder --code-complexity
-
-Then you can apply everything is left. But I strongly recommend to add
-validations one by one, right after all issues are fixed from previous one.
-Now it is not possible to compare results on feature branches without scripting,
-so you must be careful, if you want to use all suitable validators and results
-are not as good as it can be.
-
-There are few rails specific validators, but the rules are the same. Security is
-the first priority:
-
-    $ warder --rails-security
-
-You may also want to see some advice, regarding rails best practices:
-
-    $ warder --rails-advice
-
-but be careful with it, some reported advices may conflict with another
-validators.
-
-You may also see, how your rails app meets Sandi Metz rules:
-
-    $ warder --sandi-rules
-
-You can validate not only ruby files, but also coffeescript files:
-
-    $ warder --coffee-lint
-
-## Installation
-
-Add this line to your application's Gemfile:
-
-    gem 'warder'
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install warder
-
-## Usage
-
-First of all, RTFM!
-
-    $ warder --help
-
-to see all supported scanners.
-If you are too lazy, you will be confused with results.
-
-    $ warder
-    
-to see that everything is good (actually no one validator used) and you don't
-need to fix any issues :)
-
-You also can use shortcuts:
-
-    $ warder --all
-    
-to run all validations, even ones you don't really need.
-
-To run only rails related validations:
-
-    $ warder --rails
-
-or to validate your ruby project:
-
-    $ warder --all --no-rails
-
-if you so tired looking at your code issues, you can use silent mode
-
-    $ warder --quiet
-    
-and you just will get result by exit code.
-
-But if you, or your CI is really interested in statistics, there is statistics
-mode for you:
-
-    $ warder --quiet --stats
-
-if you working on multiple projects, you can pass path to another project
-as an argument:
-
-    $ warder --quiet /path/to/another/project
-    
-The best thing I can do with warder is validate project itself, so anyone can
-see, that it is not so hard to write good ruby code. Just check build status on
-[Travis CI](https://travis-ci.org/yltsrc/warder).
-
-## Contributing
-
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request

data/Rakefile

@@ -1,53 +0,0 @@
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-require 'cucumber/rake/task'
-
-namespace :spec do
-  desc 'Run specs that should pass'
-  RSpec::Core::RakeTask.new(:ok) do |t|
-    t.rspec_opts = '--tag ~wip'
-    t.pattern = './spec/**/*_spec.rb'
-  end
-
-  desc 'Run specs that are being worked on'
-  RSpec::Core::RakeTask.new(:wip) do |t|
-    t.rspec_opts = '--color --tag wip'
-    t.pattern = './spec/**/*_spec.rb'
-  end
-
-  desc 'Run all specs'
-  RSpec::Core::RakeTask.new(:all) do |t|
-    t.rspec_opts = '--color'
-    t.pattern = './spec/**/*_spec.rb'
-  end
-end
-
-namespace :cucumber do
-  desc 'Run features that should pass'
-  Cucumber::Rake::Task.new(:ok) do |t|
-    t.fork = true # You may get faster startup if you set this to false
-    t.profile = 'ok'
-  end
-
-  desc 'Run features that are being worked on'
-  Cucumber::Rake::Task.new(:wip) do |t|
-    t.fork = true # You may get faster startup if you set this to false
-    t.profile = 'wip'
-  end
-
-  desc 'Run all features'
-  Cucumber::Rake::Task.new(:all) do |t|
-    t.fork = true # You may get faster startup if you set this to false
-    t.profile = 'default'
-  end
-end
-
-desc 'Alias for cucumber:ok'
-task cucumber: 'cucumber:ok'
-
-desc 'Alias for spec:ok'
-task spec: 'spec:ok'
-
-task wip: %w(spec:wip cucumber:wip)
-task all: %w(spec:all cucumber:all)
-task default: %w(spec cucumber)

data/cucumber.yml

@@ -1,4 +0,0 @@
-<% std_opts = "--color --format 'pretty'" %>
-default: <%= std_opts %> --strict features
-ok: <%= std_opts %> --strict --tags ~@wip features
-wip: <%= std_opts %> --tags @wip:1 --wip features

data/features/checks_for_all_issues.feature

@@ -1,36 +0,0 @@
-Feature: checks for all issues
-  In order to find all issues
-  As a ruby developer
-  I want to run warder with --all option
-
-  Scenario: run warder with enabled all option
-    Given I have valid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --all`
-    Then warder detects style guide issues
-    Then warder detects magick numbers issues
-    Then warder detects code complexity issues
-    Then warder detects code duplication issues
-    Then warder detects code smell issues
-    Then warder detects sandi rules violations
-    Then warder detects rails best practices issues
-    Then warder detects rails security issues
-    Then warder detects gem freshness issues
-    Then warder detects coffee lint issues
-    Then the exit status should be 0
-
-  Scenario: run warder with enabled rails option on invalid project
-    Given I have invalid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --all`
-    Then warder detects style guide issues
-    Then warder detects magick numbers issues
-    Then warder detects code complexity issues
-    Then warder detects code duplication issues
-    Then warder detects code smell issues
-    Then warder detects sandi rules violations
-    Then warder detects rails best practices issues
-    Then warder detects rails security issues
-    Then warder detects gem freshness issues
-    Then warder detects coffee lint issues
-    Then the exit status should be 10

data/features/checks_for_rails_best_practices.feature

@@ -1,25 +0,0 @@
-Feature: checks for rails best practices advices
-  In order to get rails advices
-  As a ruby developer
-  I want to run warder with --rails-advice option
-
-  Scenario: run warder with enabled rails advice option
-    Given I have valid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --rails-advice`
-    Then warder detects rails best practices issues
-    Then the exit status should be 0
-
-  Scenario: run warder with enabled rails advice option on invalid project
-    Given I have invalid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --rails-advice`
-    Then warder detects rails best practices issues
-    Then the exit status should be 1
-
-  Scenario: run warder with disabled rails advice option on invalid project
-    Given I have invalid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --no-rails-advice`
-    Then warder does nothing
-    Then the exit status should be 0

data/features/checks_for_rails_related_issues.feature

@@ -1,27 +0,0 @@
-Feature: checks for rails related issues
-  In order to find rails related issues
-  As a ruby developer
-  I want to run warder with --rails option
-
-  Scenario: run warder with enabled rails option
-    Given I have valid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --rails`
-    Then warder detects rails best practices issues
-    Then warder detects rails security issues
-    Then the exit status should be 0
-
-  Scenario: run warder with enabled rails option on invalid project
-    Given I have invalid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --rails`
-    Then warder detects rails best practices issues
-    Then warder detects rails security issues
-    Then the exit status should be 2
-
-  Scenario: run warder with disabled rails option on invalid project
-    Given I have invalid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --no-rails`
-    Then warder does nothing
-    Then the exit status should be 0

data/features/checks_for_rails_security_issues.feature

@@ -1,25 +0,0 @@
-Feature: checks for rails related security issues
-  In order to find security issues
-  As a ruby developer
-  I want to run warder with --rails-security option
-
-  Scenario: run warder with enabled rails security option
-    Given I have valid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --rails-security`
-    Then warder detects rails security issues
-    Then the exit status should be 0
-
-  Scenario: run warder with enabled rails security option on invalid project
-    Given I have invalid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --rails-security`
-    Then warder detects rails security issues
-    Then the exit status should be 1
-
-  Scenario: run warder with disabled rails security option on invalid project
-    Given I have invalid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --no-rails-security`
-    Then warder does nothing
-    Then the exit status should be 0

data/features/checks_for_sandi_metz_rules.feature

@@ -1,25 +0,0 @@
-Feature: checks for Sandi Metz rules violations
-  In order to find Sandi Metz rules violations
-  As a ruby developer
-  I want to run warder with --sandi-rules option
-
-  Scenario: run warder with enabled sandi rules option
-    Given I have valid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --sandi-rules`
-    Then warder detects sandi rules violations
-    Then the exit status should be 0
-
-  Scenario: run warder with enabled sandi rules option on invalid project
-    Given I have invalid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --sandi-rules`
-    Then warder detects sandi rules violations
-    Then the exit status should be 1
-
-  Scenario: run warder with disabled sandi rules option on invalid project
-    Given I have invalid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --no-sandi-rules`
-    Then warder does nothing
-    Then the exit status should be 0

data/features/checks_for_vulnerable_gems.feature

@@ -1,25 +0,0 @@
-Feature: checks for vulnerable gems
-  In order to find vulnerable gems
-  As a ruby developer
-  I want to run warder with --bundle-audit option
-
-  Scenario: run warder with enabled bundle audit option
-    Given I have valid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --bundle-audit`
-    Then warder detects gem freshness issues
-    Then the exit status should be 0
-
-  Scenario: run warder with enabled bundle audit option on invalid file
-    Given I have invalid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --bundle-audit`
-    Then warder detects gem freshness issues
-    Then the exit status should be 1
-
-  Scenario: run warder with disabled bundle audit option on invalid file
-    Given I have invalid_rails_app project in directory
-    And I am on project directory
-    When I run `warder --no-bundle-audit`
-    Then warder does nothing
-    Then the exit status should be 0

data/features/detects_code_complexity.feature

@@ -1,29 +0,0 @@
-Feature: detects code complexity
-  In order to find code complexity
-  As a ruby developer
-  I want to run warder with --code-complexity option
-
-  Scenario: run warder with enabled code complexity option
-    Given I have valid file in directory
-    When I run `warder --code-complexity`
-    Then warder detects code complexity issues
-    Then the exit status should be 0
-
-  Scenario: run warder with enabled code complexity option on invalid file
-    Given I have invalid_code_complexity file in directory
-    When I run `warder --code-complexity`
-    Then warder detects code complexity issues
-    Then the exit status should be 1
-
-  Scenario: run warder with enabled code complexity option on valid file only
-    Given I have valid file in directory
-    And I have invalid_code_complexity file in directory
-    When I run `warder --code-complexity valid.rb`
-    Then warder does nothing
-    Then the exit status should be 0
-
-  Scenario: run warder with disabled code complexity option on invalid file
-    Given I have invalid_code_complexity file in directory
-    When I run `warder --no-code-complexity`
-    Then warder does nothing
-    Then the exit status should be 0

data/features/detects_code_duplication.feature

@@ -1,32 +0,0 @@
-Feature: detects code duplication
-  In order to find code duplication
-  As a ruby developer
-  I want to run warder with --code-duplication option
-
-  Scenario: run warder with enabled code duplication option
-    Given I have valid file in directory
-    When I run `warder --code-duplication`
-    Then warder detects code duplication issues
-    Then the exit status should be 0
-
-  Scenario: run warder with enabled code duplication option on invalid file
-    Given I have invalid_code_duplication file in directory
-    When I set the environment variables to:
-      | variable   | value |
-      | FLAY_SCORE | 15    |
-    And I run `warder --code-duplication`
-    Then warder detects code duplication issues
-    Then the exit status should be 1
-
-  Scenario: run warder with enabled code duplication option on valid file only
-    Given I have valid file in directory
-    And I have invalid_code_duplication file in directory
-    When I run `warder --code-duplication valid.rb`
-    Then warder does nothing
-    Then the exit status should be 0
-
-  Scenario: run warder with disabled code duplication option on invalid file
-    Given I have invalid_code_duplication file in directory
-    When I run `warder --no-code-duplication`
-    Then warder does nothing
-    Then the exit status should be 0