cucumber-rails 2.2.0 → 2.3.0

data/features/choose_javascript_database_strategy.feature

@@ -1,125 +0,0 @@
-Feature: Choose javascript database strategy
-
-  Whilst 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
-    When I write to "features/step_definitions/widget_steps.rb" with:
-      """
-      When('I create {int} widgets') do |number|
-        number.times { Widget.create! }
-      end
-
-      Then('I should have {int} widgets') do |number|
-        expect(Widget.count).to eq(number)
-      end
-
-      Then('the DatabaseCleaner strategy should be {word}') do |strategy_name|
-        expect(DatabaseCleaner.cleaners.values.first.strategy.to_s).to match(/#{strategy_name}/i)
-      end
-      """
-
-  Scenario: Set the strategy to truncation and run a javascript scenario.
-    When 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:
-          When I create 2 widgets
-
-        @javascript
-        Scenario:
-          When I create 3 widgets
-          Then the DatabaseCleaner strategy should be truncation
-          And 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 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.
-    When I append to "features/env.rb" with:
-      """
-      Cucumber::Rails::Database.javascript_strategy = :deletion
-      """
-    And I write to "features/widgets.feature" with:
-      """
-      @javascript
-      Feature:
-        Background:
-          When I create 2 widgets
-
-        Scenario:
-          When I create 3 widgets
-          Then I should have 5 widgets
-
-        Scenario:
-          Then I should have 2 widgets
-      """
-    And 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.
-    When 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 run the cukes
-    Then the feature run should pass with:
-      """
-      2 scenarios (2 passed)
-      3 steps (3 passed)
-      """

data/features/configuration.feature

@@ -1,48 +0,0 @@
-Feature: Cucumber Rails Configuration
-
-  In order to configure how Cucumber-Rails runs
-  As a developer
-  I should be able to alter the settings of my project
-
-  Scenario: Default configuration
-    Given I have created a new Rails app with no database and installed cucumber-rails
-    When I write to "features/config.feature" with:
-      """
-      Feature: Rack Test Methods
-        Scenario: Default Methods are added to the World
-          Then Rack Test should be mixed into the Cucumber World
-      """
-    When I write to "features/step_definitions/config_steps.rb" with:
-      """
-      Then('Rack Test should be mixed into the Cucumber World') do
-        expect(self.class.ancestors).to include(Rack::Test::Methods)
-      end
-      """
-    And I run `bundle exec rake cucumber`
-    Then the feature run should pass with:
-      """
-      1 scenario (1 passed)
-      1 step (1 passed)
-      """
-
-  Scenario: Altered configuration
-    Given I have created a new Rails app with no database and installed cucumber-rails
-    And I set the environment variable "CR_REMOVE_RACK_TEST_HELPERS" to "true"
-    When I write to "features/config.feature" with:
-      """
-      Feature: Rack Test Methods
-        Scenario: Rack Test Methods can be removed from the world
-          Then Rack Test should not be mixed into the Cucumber World
-      """
-    When I write to "features/step_definitions/config_steps.rb" with:
-      """
-      Then('Rack Test should not be mixed into the Cucumber World') do
-        expect(self.class.ancestors).not_to include(Rack::Test::Methods)
-      end
-      """
-    And I run `bundle exec rake cucumber`
-    Then the feature run should pass with:
-      """
-      1 scenario (1 passed)
-      1 step (1 passed)
-      """

data/features/database_cleaner.feature

@@ -1,131 +0,0 @@
-Feature: Database Cleaner
-
-  Scenario: Create records in background with database_cleaner
-    Given I have created a new Rails app and installed cucumber-rails
-    When I write to "features/widgets.feature" with:
-      """
-      Feature: Create widgets
-        Background: 2 initial widgets
-          Given I have 2 widgets
-
-        Scenario: Add 3 widgets
-          When I create 3 more widgets
-          Then I should have 5 widgets
-
-        Scenario: Add 7 widgets
-          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 {int} widgets') do |number|
-        number.times do |i|
-          Widget.create! name: "Widget #{Widget.count + i}"
-        end
-      end
-
-      When('I create {int} more widgets') do |number|
-        number.times do |i|
-          Widget.create! name: "Widget #{Widget.count + i}"
-        end
-      end
-
-      Then('I should have {int} widgets') do |number|
-        expect(Widget.count).to eq(number)
-      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)
-      """
-
-  Scenario: Create records in background with database_cleaner-active_record
-    Given I have created a new Rails app and installed cucumber-rails with database_cleaner-active_record
-    When I write to "features/widgets.feature" with:
-      """
-      Feature: Create widgets
-        Background: 2 initial widgets
-          Given I have 2 widgets
-
-        Scenario: Add 3 widgets
-          When I create 3 more widgets
-          Then I should have 5 widgets
-
-        Scenario: Add 7 widgets
-          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 {int} widgets') do |number|
-        number.times do |i|
-          Widget.create! name: "Widget #{Widget.count + i}"
-        end
-      end
-
-      When('I create {int} more widgets') do |number|
-        number.times do |i|
-          Widget.create! name: "Widget #{Widget.count + i}"
-        end
-      end
-
-      Then('I should have {int} widgets') do |number|
-        expect(Widget.count).to eq(number)
-      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)
-      """
-
-  Scenario: Create records in background without using database_cleaner
-    Given I have created a new Rails app and installed cucumber-rails without database_cleaner
-    When I write to "features/widgets.feature" with:
-      """
-      Feature: Create widgets
-        Background: 2 initial widgets
-          # Note this creates 2 widgets each time
-          Given I have 2 widgets
-
-        Scenario: Add 3 widgets
-          When I create 3 more widgets
-          Then I should have 5 widgets
-
-        Scenario: Add 7 widgets
-          When I create 7 more widgets
-          Then I should have 14 widgets
-      """
-    And I run `rails generate model widget name:string`
-    And I write to "features/step_definitions/widget_steps.rb" with:
-      """
-      Given('I have {int} widgets') do |number|
-        number.times do |i|
-          Widget.create! name: "Widget #{Widget.count + i}"
-        end
-      end
-
-      When('I create {int} more widgets') do |number|
-        number.times do |i|
-          Widget.create! name: "Widget #{Widget.count + i}"
-        end
-      end
-
-      Then('I should have {int} widgets') do |number|
-        expect(Widget.count).to eq(number)
-      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,49 +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
-    When 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:
-      """
-      When('I create {int} widgets') do |number|
-        number.times do |i|
-          Widget.create! name: "Widget #{Widget.count + i}"
-        end
-      end
-
-      Then('I should have {int} widgets') do |number|
-        expect(Widget.count).to eq(number)
-      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,109 +0,0 @@
-Feature: Emulate Javascript
-
-  Background:
-    Given I have created a new Rails app and installed cucumber-rails
-    And I force selenium to run Firefox in headless mode
-    When I run `rails generate scaffold widget name:string`
-    And I write to "features/step_definitions/widget_steps.rb" with:
-    """
-      Given('there is a widget named {string}') do |name|
-        FactoryBot.create(:widget, name: name)
-      end
-
-      When('I am on the widgets page') do
-        visit widgets_path
-      end
-
-      Then('I should see {string}') do |text|
-        expect(page).to have_content(text)
-      end
-      """
-    And I write to "features/support/factories/widget.rb" with:
-      """
-      FactoryBot.define do
-        factory :widget do
-          name { 'testwidget' }
-        end
-      end
-      """
-
-  Scenario: See a widget
-    When I write to "features/widgets.feature" with:
-      """
-      @javascript
-      Feature: Widget inventory
-        Scenario: Delete a widget
-          Given there is a widget named "wrench"
-          And I am on the widgets page
-          Then I should see "wrench"
-      """
-    And 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
-    When 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/widgets.feature" with:
-      """
-      Feature: Widget inventory
-        Scenario: Delete a widget
-          Given there is a widget named "wrench"
-          And I am on the session establish page
-          And I am on 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 append to "features/step_definitions/widget_steps.rb" with:
-      # TODO: Remove the newline below (Required) once bug is fixed: https://github.com/cucumber/aruba/issues/662
-      """
-
-      Given('I am on the session establish page') do
-        visit session_establish_path
-      end
-
-      When('I follow {string}') do |link|
-        click_link(link)
-      end
-
-      Then('I should not see {string}') do |text|
-        expect(page).not_to have_content(text)
-      end
-
-      Then('I should be on the widgets page') do
-        current_path = URI.parse(current_url).path
-        expect(current_path).to eq(widgets_path)
-      end
-      """
-    And 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)
-      """