capistrano/Rakefile

require "bundler/gem_tasks"
require "cucumber/rake/task"
require "rspec/core/rake_task"
require "rubocop/rake_task"

task default: %i(spec rubocop)
RSpec::Core::RakeTask.new

Cucumber::Rake::Task.new(:features)

desc "Run RuboCop checks"
RuboCop::RakeTask.new
initial commit 2013-02-01 09:19:14 +00:00			`require "bundler/gem_tasks"`
Cucumber tests will now run on the latest Vagrant This removes the dependency on the `kuroko` gem and uses the Vagrant command line application to control the virtual environment. The `vagrant` command should be in your path, but if it isn't the path can be set with the `VAGRANT_BIN` environment variable. This may even work on older versions of Vagrant, but they are untested. The `VagrantHelpers` module was added to mimic some of the API that was provided by `kuroko`. The `RemoteCommandHelpers` module was modified to accommodate those changes. Any non-zero exit status on a remote command will raise a `VagrantHelpers::VagrantSSHCommandError` and should be expected by any tests using the command helpers. All existing tests work as expected. In addition, a couple of minor changes were made. The TestApp utilizes the Pathname library but does not require it. This was causing the suite to fail for me so I added an explicit require. Also, the test for the existence of a release directory would give a false positive on subsequent runs if the `KEEP_RUNNING` option was used. I added an `at_exit` that removes the test deployment directory to clean up the box for the next run. Documentation was also added to the README for how to run the test suites. 2014-04-22 15:36:44 +00:00			`require "cucumber/rake/task"`
			`require "rspec/core/rake_task"`
Add RuboCop lint to default rake task 2016-01-23 21:07:52 +00:00			`require "rubocop/rake_task"`
add default rake task for travis 2013-02-08 09:20:23 +00:00
Fix RuboCop 0.48 violations 2017-03-26 22:50:35 +00:00			`task default: %i(spec rubocop)`
add default rake task for travis 2013-02-08 09:20:23 +00:00			`RSpec::Core::RakeTask.new`
Cucumber tests will now run on the latest Vagrant This removes the dependency on the `kuroko` gem and uses the Vagrant command line application to control the virtual environment. The `vagrant` command should be in your path, but if it isn't the path can be set with the `VAGRANT_BIN` environment variable. This may even work on older versions of Vagrant, but they are untested. The `VagrantHelpers` module was added to mimic some of the API that was provided by `kuroko`. The `RemoteCommandHelpers` module was modified to accommodate those changes. Any non-zero exit status on a remote command will raise a `VagrantHelpers::VagrantSSHCommandError` and should be expected by any tests using the command helpers. All existing tests work as expected. In addition, a couple of minor changes were made. The TestApp utilizes the Pathname library but does not require it. This was causing the suite to fail for me so I added an explicit require. Also, the test for the existence of a release directory would give a false positive on subsequent runs if the `KEEP_RUNNING` option was used. I added an `at_exit` that removes the test deployment directory to clean up the box for the next run. Documentation was also added to the README for how to run the test suites. 2014-04-22 15:36:44 +00:00
			`Cucumber::Rake::Task.new(:features)`

Make entire Rubocop suite run by default. 2016-03-01 14:39:51 +00:00			`desc "Run RuboCop checks"`
			`RuboCop::RakeTask.new`