cucumber-rails 1.7.0 → 2.3.0

data/features/choose_javascript_database_strategy.feature

@@ -1,145 +0,0 @@
-Feature: Choose javascript database strategy
-
-  When running a scenario with the @javascript tag, Capybara will fire up a web server
-  in the same process in a separate thread to your cukes. By default, this means ActiveRecord will give it a
-  separate database connection, which in turn means data you put into your database from
-  Cucumber step definitions (e.g. using FactoryBot) won't be visible to the web server
-  until the database transaction is committed.
-
-  So if you use a transaction strategy for cleaning up your database at the end of a scenario,
-  it won't work for javascript scenarios by default.
-
-  There are two ways around this. One is to switch to a truncation strategy for javascript
-  scenarios. This is slower, but more reliable.
-
-  The alternative is to patch ActiveRecord to share a single database connection between
-  threads. This means you still get the speed benefits of using a transaction to roll back
-  your database, but you run the risk of the two threads stomping on one another as they
-  talk to the database.
-
-  Right now, the default behavior is to use truncation, but you can override this by telling
-  cucumber-rails which strategy to use for javascript scenarios.
-
-  The deletion strategy can be quicker for situations where truncation causes locks which
-  has been reported by some Oracle users.
-
-  Background:
-    Given I have created a new Rails app and installed cucumber-rails
-    And I have a "Widget" ActiveRecord model object
-
-  Scenario: Set the strategy to truncation and run a javascript scenario.
-    Given I append to "features/env.rb" with:
-      """
-      DatabaseCleaner.strategy = :transaction
-      Cucumber::Rails::Database.javascript_strategy = :truncation
-      """
-    And I write to "features/widgets.feature" with:
-      """
-      Feature:
-        Background:
-          Given I have created 2 widgets
-
-        @javascript
-        Scenario:
-          Then the DatabaseCleaner strategy should be truncation
-          When I create 3 widgets
-          Then I should have 5 widgets
-
-        @javascript
-        Scenario:
-          Then the DatabaseCleaner strategy should be truncation
-          And I should have 2 widgets
-
-        Scenario:
-          Then the DatabaseCleaner strategy should be transaction
-          And I should have 2 widgets
-      """
-    And I write to "features/step_definitions/widget_steps.rb" with:
-      """
-      Given /created? (\d) widgets/ do |num|
-        num.to_i.times { Widget.create! }
-      end
-
-      Then /should have (\d) widgets/ do |num|
-        Widget.count.should == num.to_i
-      end
-
-     Then /^the DatabaseCleaner strategy should be (\w+)$/ do |strategy_name|
-        DatabaseCleaner.connections.first.strategy.to_s.should =~ /#{strategy_name}/i
-      end
-      """
-    When I run the cukes
-    Then the feature run should pass with:
-       """
-       3 scenarios (3 passed)
-       10 steps (10 passed)
-       """
-
- Scenario: Set the strategy to deletion and run a javascript scenario.
-    Given I append to "features/env.rb" with:
-      """
-      Cucumber::Rails::Database.javascript_strategy = :deletion
-      """
-    And I write to "features/widgets.feature" with:
-      """
-      @javascript
-      Feature:
-        Background:
-          Given I have created 2 widgets
-
-        Scenario:
-          When I create 3 widgets
-          Then I should have 5 widgets
-
-        Scenario:
-          Then I should have 2 widgets
-      """
-    And I write to "features/step_definitions/widget_steps.rb" with:
-      """
-      Given /created? (\d) widgets/ do |num|
-        num.to_i.times { Widget.create! }
-      end
-
-      Then /should have (\d) widgets/ do |num|
-        Widget.count.should == num.to_i
-      end
-      """
-    When I run the cukes
-    Then the feature run should pass with:
-       """
-       2 scenarios (2 passed)
-       5 steps (5 passed)
-     """
-
-  Scenario: Set the strategy to truncation with an except option and run a javascript scenario.
-    Given I append to "features/env.rb" with:
-      """
-     Cucumber::Rails::Database.javascript_strategy = :truncation, {:except=>%w[widgets]}
-      """
-    And I write to "features/widgets.feature" with:
-      """
-      @javascript
-      Feature:
-        Scenario:
-          When I create 3 widgets
-          Then I should have 3 widgets
-
-        Scenario:
-          Then I should have 3 widgets
-      """
-    And I write to "features/step_definitions/widget_steps.rb" with:
-      """
-      Given /created? (\d) widgets/ do |num|
-        num.to_i.times { Widget.create! }
-      end
-
-      Then /should have (\d) widgets/ do |num|
-        Widget.count.should == num.to_i
-      end
-      """
-    When I run the cukes
-    Then the feature run should pass with:
-       """
-       2 scenarios (2 passed)
-       3 steps (3 passed)
-       """

data/features/database_cleaner.feature

@@ -1,44 +0,0 @@
-Feature: DatabaseCleaner
-
-  Scenario: Create records in background
-    Given I have created a new Rails app and installed cucumber-rails
-    And I write to "features/widgets.feature" with:
-      """
-      Feature: Create widgets
-        Background: some widdgets
-          Given I have 2 widgets
-
-        Scenario: Add 3
-          When I create 3 more widgets
-          Then I should have 5 widgets
-
-        Scenario: Add 7
-          When I create 7 more widgets
-          Then I should have 9 widgets
-      """
-    And I run `rails generate model widget name:string`
-    And I write to "features/step_definitions/widget_steps.rb" with:
-      """
-      Given /^I have (\d+) widgets$/ do |n|
-        n.to_i.times do |i|
-          Widget.create! name: "Widget #{Widget.count + i}"
-        end
-      end
-
-      When /^I create (\d+) more widgets$/ do |n|
-        n.to_i.times do |i|
-          Widget.create! name: "Widget #{Widget.count + i}"
-        end
-      end
-
-      Then /^I should have (\d+) widgets$/ do |n|
-        Widget.count.should == n.to_i
-      end
-      """
-    And I run `bundle exec rake db:migrate`
-    And I run `bundle exec rake cucumber`
-    Then the feature run should pass with:
-       """
-       2 scenarios (2 passed)
-       6 steps (6 passed)
-       """

data/features/disable_automatic_database_cleaning.feature

@@ -1,55 +0,0 @@
-Feature: Disable automatic database cleaning
-
-  By default, a set of Before/After hooks are installed to
-  invoke database_cleaner on every scenario except those tagged
-  "@no-database-cleaner". Sometimes when a user is switching between
-  cleaning strategies, this can initiate an undesired database
-  transaction.
-
-  To avoid the need for users making frequent strategy switches to apply
-  this tag, a configuration option is provided so that the user can
-  control the invocation of database_cleaner explicitly.
-
-  Scenario: Disabling automatic cleaning
-    Given I have created a new Rails app and installed cucumber-rails
-    And I append to "features/env.rb" with:
-      """
-      Cucumber::Rails::Database.autorun_database_cleaner = false
-      """
-    And I write to "features/widgets.feature" with:
-      """
-      Feature: Create widgets
-        Scenario: Create 3 widgets
-          When I create 3 widgets
-          Then I should have 3 widgets
-
-        Scenario: Create 5 widgets
-          When I create 5 widgets
-          Then I should have 8 widgets
-      """
-    And I run `rails generate model widget name:string`
-    And I write to "features/step_definitions/widget_steps.rb" with:
-      """
-      Given /^I have (\d+) widgets$/ do |n|
-        n.to_i.times do |i|
-          Widget.create! name: "Widget #{Widget.count + i}"
-        end
-      end
-
-      When /^I create (\d+) widgets$/ do |n|
-        n.to_i.times do |i|
-          Widget.create! name: "Widget #{Widget.count + i}"
-        end
-      end
-
-      Then /^I should have (\d+) widgets$/ do |n|
-        Widget.count.should == n.to_i
-      end
-     """
-    And I run `bundle exec rake db:migrate`
-    And I run `bundle exec rake cucumber`
-    Then the feature run should pass with:
-       """
-       2 scenarios (2 passed)
-       4 steps (4 passed)
-       """

data/features/emulate_javascript.feature

@@ -1,94 +0,0 @@
-Feature: Emulate Javascript
-
-  Scenario: See a widget
-    Given I have created a new Rails app and installed cucumber-rails
-    And I force selenium to run Firefox in headless mode
-    And I run `rails generate scaffold widget name:string`
-    And I write to "features/f.feature" with:
-      """
-      @javascript
-      Feature: Widget inventory
-        Scenario: Delete a widget
-          Given there is a widget named "wrench"
-          When I go to the widgets page
-          Then I should see "wrench"
-      """
-    And I write to "features/step_definitions/s.rb" with:
-      """
-      Given /^there is a widget named "([^"]*)"$/ do |name|
-        FactoryBot.create(:widget, name: name)
-      end
-      """
-    And I write to "features/support/factories.rb" with:
-      """
-      FactoryBot.define do
-        factory :widget do
-          name { 'testwidget' }
-        end
-      end
-      """
-    When I run `bundle exec rake db:migrate`
-    And I run `bundle exec rake cucumber`
-    Then the feature run should pass with:
-       """
-       1 scenario (1 passed)
-       3 steps (3 passed)
-       """
-
-  Scenario: Pass on the CSRF token
-    Given I have created a new Rails app and installed cucumber-rails
-    And I run `rails generate scaffold widget name:string`
-    And I run `sed -i -e 's/forgery_protection *= false/forgery_protection = true/' config/environments/test.rb`
-    And I run `rails generate controller session establish`
-    And I write to "app/controllers/session_controller.rb" with:
-      """
-      class SessionController < ApplicationController
-        def establish
-          session[:verified] = true
-        end
-      end
-      """
-    And I write to "app/controllers/application_controller.rb" with:
-      """
-      class ApplicationController < ActionController::Base
-        protect_from_forgery
-        before_action except: :establish do
-          render text: "denied", status: :forbidden and return false unless session[:verified]
-        end
-      end
-      """
-    And I write to "features/f.feature" with:
-      """
-      Feature: Widget inventory
-        Scenario: Delete a widget
-          Given there is a widget named "wrench"
-          When I go to the session establish page
-          And I go to the widgets page
-          Then I should see "wrench"
-          When I follow "Destroy"
-          Then I should not see "denied"
-          And I should be on the widgets page
-          And I should not see "wrench"
-      """
-    And I write to "features/step_definitions/s.rb" with:
-      """
-      Given /^there is a widget named "([^"]*)"$/ do |name|
-        FactoryBot.create(:widget, name: name)
-      end
-      """
-    And I write to "features/support/factories.rb" with:
-      """
-      FactoryBot.define do
-        factory :widget do
-          name { 'testwidget' }
-        end
-      end
-      """
-    When I run `bundle exec rake db:migrate`
-    And I run `bundle exec rake cucumber`
-    Then the feature run should pass with:
-       """
-       1 scenario (1 passed)
-       8 steps (8 passed)
-       """
-

data/features/install_cucumber_rails.feature

@@ -1,14 +0,0 @@
-Feature: Rails
-  In order to take over the world
-  Cucumber-Rails should work on major versions
-  of Rails and Ruby, with Capybara, Spork and DatabaseCleaner
-
-  Scenario: Install Cucumber-Rails
-    Given I have created a new Rails app and installed cucumber-rails
-    Then the following files should exist:
-      | config/cucumber.yml                    |
-      | script/cucumber                        |
-      | features/support/env.rb                |
-      | features/step_definitions/.gitkeep     |
-      | lib/tasks/cucumber.rake                |
-    And the file "features/support/env.rb" should contain "require 'cucumber/rails'"

data/features/no_database.feature

@@ -1,61 +0,0 @@
-Feature: No Database
-  Allow Cucumber to work with a Rails app without a database
-
-  @fails-on-travis
-  Scenario: No ActiveRecord and DatabaseCleaner
-    Given I have created a new Rails app with no database and installed cucumber-rails
-    # Turn off ActiveRecord
-    And I write to "config/application.rb" with:
-      """
-      require File.expand_path('../boot', __FILE__)
-
-      require 'action_controller/railtie'
-      require 'action_mailer/railtie'
-      require 'rails/test_unit/railtie'
-
-      Bundler.require(:default, Rails.env) if defined?(Bundler)
-
-      module TestApp
-        class Application < Rails::Application
-          config.encoding = "utf-8"
-          config.filter_parameters += [:password]
-        end
-      end
-      """
-    And I overwrite "features/support/env.rb" with:
-      """
-      require 'cucumber/rails'
-      """
-    And I remove the 'database_cleaner' gem from the Gemfile
-    And I remove the 'sqlite' gem from the Gemfile
-    And I write to "app/controllers/posts_controller.rb" with:
-      """
-      class PostsController < ApplicationController
-        def index
-          raise "There is an error in index"
-        end
-      end
-      """
-    And I write to "config/routes.rb" with:
-      """
-      TestApp::Application.routes.draw do
-        resources :posts
-      end
-      """
-    And I write to "features/posts.feature" with:
-      """
-      Feature: posts
-        Scenario: See them
-          When I do it
-      """
-    And I write to "features/step_definitions/posts_steps.rb" with:
-      """
-      When /^I do it$/ do
-        visit '/posts'
-      end
-      """
-    And I run `bundle exec rake cucumber`
-    Then it should fail with:
-      """
-      There is an error in index
-      """

data/features/raising_errors.feature

@@ -1,16 +0,0 @@
-Feature: Raise Errors
-
-  Scenario: Raise error for undefined route
-    Given I have created a new Rails app "test-app" with no database and installed cucumber-rails
-    And I write to "features/tests.feature" with:
-      """
-      Feature: Tests
-        Scenario: Tests
-          When I go to the products page
-      """
-    And I run `bundle exec cucumber`
-    Then it should fail with:
-      """
-      1 scenario (1 failed)
-      1 step (1 failed)
-      """

data/features/rerun_profile.feature

@@ -1,46 +0,0 @@
-Feature: Rerun profile
-  In order to concentrate on failing features
-  As a Rails developer working with Cucumber
-  I want to rerun only failing features
-
-  Scenario: Rerun
-    Given I have created a new Rails app and installed cucumber-rails
-    And a file named "rerun.txt" with:
-      """
-      features/rerun_test.feature:2
-      features/rerun_test.feature:5
-      """
-    And a file named "features/rerun_test.feature" with:
-      """
-      Feature: Rerun test
-        Scenario: failing before
-          Given fixed now
-
-        Scenario: still failing
-          Given broken
-
-        Scenario: always passing
-          Given passing
-      """
-    And a file named "features/step_definitions/rerun_steps.rb" with:
-      """
-      Given /fixed now/ do
-        puts "All fixed now"
-      end
-
-      Given /broken/ do
-        raise "I'm broken"
-      end
-
-      Given /passing/ do
-        puts "I've always been passing"
-      end
-      """
-    When I run `bundle exec cucumber -p rerun`
-    Then it should fail with:
-      """
-      2 scenarios (1 failed, 1 passed)
-      2 steps (1 failed, 1 passed)
-      """
-    And the file "rerun.txt" should not contain "features/rerun_test.feature:2"
-    And the file "rerun.txt" should contain "features/rerun_test.feature:5"