spreewald 2.2.3 → 2.2.4

data/tests/rails-3_capybara-1/config/cucumber.yml

@@ -1,2 +0,0 @@
-default: --require features --require features/shared features/shared
-

data/tests/rails-3_capybara-1/config/database.yml

@@ -1,7 +0,0 @@
-development:
-  adapter: sqlite3
-  database: ":memory:"
-
-test:
-  adapter: sqlite3
-  database: ":memory:"

data/tests/rails-3_capybara-1/features/support/paths.rb

@@ -1,16 +0,0 @@
-module NavigationHelpers
-  
-  def path_to(page_name)
-    case page_name
-    when /^"(.*)"$/
-      $1
-
-    else
-      raise "Can't find mapping from \"#{page_name}\" to a path.\n" +
-        "Now, go and add a mapping in #{__FILE__}"
-    end
-  end
-  
-end
-
-World(NavigationHelpers)

data/tests/rails-3_capybara-1/features/support/selectors.rb

@@ -1,52 +0,0 @@
-module HtmlSelectorsHelpers
-  # Maps a name to a selector. Used primarily by the
-  #
-  #   When /^(.+) within (.+)$/ do |step, scope|
-  #
-  # step definitions in web_steps.rb
-  #
-  def selector_for(locator)
-    case locator
-
-    when /^a panel?$/
-      '.panel'
-
-    when /^a panels nested contents?$/
-      '.panel--nested-contents'
-
-    when /^the timeline?$/
-      '.timeline'
-
-    when /^the table row containing "(.+?)"$/
-      all('tr').detect { |tr| tr.text.include? $1 } || raise("Could not find tr containing #{$1.inspect}")
-
-    when /^a table$/
-      '.table'
-
-      # Add more mappings here.
-      # Here is an example that pulls values out of the Regexp:
-      #
-      #  when /^the (notice|error|info) flash$/
-      #    ".flash.#{$1}"
-
-      # You can also return an array to use a different selector
-      # type, like:
-      #
-      #  when /the header/
-      #    [:xpath, "//header"]
-
-      # This allows you to provide a quoted selector as the scope
-      # for "within" steps as was previously the default for the
-      # web steps:
-    when /^"(.+)"$/
-      $1
-
-    else
-      raise "Can't find mapping from \"#{locator}\" to a selector.\n" +
-              "Now, go and add a mapping in #{__FILE__}"
-    end
-  end
-
-end
-
-World(HtmlSelectorsHelpers)

data/tests/rails-3_capybara-2/Rakefile

@@ -1,18 +0,0 @@
-#!/usr/bin/env rake
-require 'cucumber/rake/task'
-
-desc 'Default: Run all specs for a specific rails version.'
-task :default => :features
-
-desc 'Run all specs for rails 3.2'
-Cucumber::Rake::Task.new(:features) do |t|
-  feature = if ENV['SINGLE_FEATURE']
-    "../../shared/features/shared/#{ ENV['SINGLE_FEATURE'] }"
-  else
-    'features/shared'
-  end
-
-  # tell cucumber where it finds it files (subdirectories and symlinks are confusing it)
-  t.cucumber_opts = "--require features --require features/shared #{feature}"
-end
-

data/tests/rails-3_capybara-2/config.ru

@@ -1,4 +0,0 @@
-# This file is used by Rack-based servers to start the application.
-
-require ::File.expand_path('../config/environment',  __FILE__)
-run SpreewaldTest::Application

data/tests/rails-4_capybara-3/features/development_steps.feature

@@ -1,8 +0,0 @@
-Feature: Development steps
-
-  Scenario: /^it should work(.+?)?$/ (without a reason)
-    Then it should work
-
-  Scenario: /^it should work(.+?)?$/ (with a given reason)
-    Then it should work once the blocker described here was fulfilled. (Feature should be pending)
-

data/tests/rails-4_capybara-3/features/email_steps.feature

@@ -1,216 +0,0 @@
-Feature: Test Spreewald's email steps
-  
-  Scenario: /^no e?mail should have been sent$/
-    When I go to "/emails/do_nothing"
-    Then the following step should succeed:
-      | no email should have been sent |
-  
-    When I go to "/emails/send_email"
-    Then the following step should fail:
-      | no email should have been sent |
-
-
-  Scenario: /^I should see "([^\"]*)" in the e?mail$/
-    When I go to "/emails/send_email"
-    Then the following step should succeed:
-      | I should see "Body" in the email |
-    But the following step should fail:
-      | I should see "XYZ" in the email |
-
-
-  Scenario: /^(an|no) e?mail should have been sent with:$/
-    When I go to "/emails/send_email"
-
-    # Test without body
-    Then the following multiline step should succeed:
-      """
-      Then an email should have been sent with:
-        '''
-        From: from@example.com
-        Reply-To: reply-to@example.com
-        To: to@example.com
-        Subject: SUBJECT
-        '''
-      """
-
-    # Test with body
-    Then the following multiline step should succeed:
-      """
-      Then an email should have been sent with:
-        '''
-        From: from@example.com
-        Reply-To: reply-to@example.com
-        To: to@example.com
-        Subject: SUBJECT
-
-        Body
-        with
-        line
-        breaks
-        '''
-      """
-
-    # Test with incorrect From header
-    Then the following multiline step should fail:
-      """
-      Then an email should have been sent with:
-        '''
-        From: other-from@example.com
-        Reply-To: reply-to@example.com
-        To: to@example.com
-        Subject: SUBJECT
-
-        Body
-        with
-        line
-        breaks
-        '''
-      """
-
-    # Test with incorrect Reply-To header
-    Then the following multiline step should fail:
-      """
-      Then an email should have been sent with:
-        '''
-        From: from@example.com
-        Reply-To: other-reply-to@example.com
-        To: to@example.com
-        Subject: SUBJECT
-
-        Body
-        with
-        line
-        breaks
-        '''
-      """
-    # Test with incorrect To header
-    Then the following multiline step should fail:
-      """
-      Then an email should have been sent with:
-        '''
-        From: from@example.com
-        Reply-To: reply-to@example.com
-        To: other-to@example.com
-        Subject: SUBJECT
-
-        Body
-        with
-        line
-        breaks
-        '''
-      """
-
-    # Test with incorrect Subject header
-    Then the following multiline step should fail:
-      """
-      Then an email should have been sent with:
-        '''
-        From: from@example.com
-        Reply-To: reply-to@example.com
-        To: to@example.com
-        Subject: OTHER-SUBJECT
-
-        Body
-        with
-        line
-        breaks
-        '''
-      """
-
-    # Test with incorrect body
-    Then the following multiline step should fail:
-      """
-      Then an email should have been sent with:
-        '''
-        From: from@example.com
-        Reply-To: reply-to@example.com
-        To: to@example.com
-        Subject: SUBJECT
-
-        Other body
-        with
-        line
-        breaks
-        '''
-      """
-
-    # Test body with multiple paragraphs
-    Then the following multiline step should fail:
-      """
-      Then an email should have been sent with:
-        '''
-        From: from@example.com
-        Reply-To: reply-to@example.com
-        To: to@example.com
-        Subject: SUBJECT
-
-        Body
-        with
-        line
-        breaks
-        
-        MORE-BODY
-        '''
-      """
-
-  Scenario: /^(an|no) e?mail should have been sent((?: |and|with|from "[^"]+"|bcc "[^"]+"|cc "[^"]+"|to "[^"]+"|the subject "[^"]+"|the body "[^"]+"|the attachments "[^"]+")+)$/
-    When I go to "/emails/send_email"
-
-    # Test with correct conditions
-    Then the following multiline step should succeed:
-      """
-      Then an email should have been sent from "from@example.com" to "to@example.com" cc "cc@example.com" bcc "bcc@example.com" and the subject "SUBJECT" and the attachments "attached_file.pdf"
-      """
-
-     # Test with wrong conditions
-    Then the following multiline step should fail:
-      """
-      Then an email should have been sent from "from@example.com" to "to@example.com" cc "cc@example.com" bcc "wrong_bcc@example.com" and the subject "SUBJECT" and the attachments "attached_file.pdf"
-      """
-
-  Scenario: /^that e?mail should have the following lines in the body:$/
-    When I go to "/emails/send_email"
-
-    # Test with correct body lines
-    Then the following multiline step should succeed:
-      """
-      Then that email should have the following lines in the body:
-        '''
-        with
-        line
-        '''
-      """
-
-     # Test with wrong body lines
-    Then the following multiline step should fail:
-      """
-      Then that email should have the following lines in the body:
-        '''
-        wrong
-        line
-        '''
-      """
-
-
-  Scenario: /^that e?mail should have the following( content in the)? body$/
-    When I go to "/emails/send_email"
-
-      # Test with correct body lines
-    Then the following multiline step should succeed:
-      """
-      Then that email should have the following content in the body:
-        '''
-        with
-        line
-        '''
-      """
-
-       # Test with wrong body lines
-    Then the following multiline step should fail:
-      """
-      Then that email should have the following body:
-        '''
-        wrong
-        line
-        '''
-      """

data/tests/rails-4_capybara-3/features/overriding.feature

@@ -1,5 +0,0 @@
-Feature: Overriding Spreewald-steps
-
-  Scenario: The developer should be able to override any Spreewald step without Cucumber raising Cucumber::Ambiguous
-    When I go to "/static_pages/overridden"
-    Then I should see "overridden value"

data/tests/rails-4_capybara-3/features/step_definitions/overriding_steps.rb

@@ -1,3 +0,0 @@
-Then /^I should see "overridden value"$/ do
-  expect(page).to have_content('overridden value')
-end

data/tests/rails-4_capybara-3/features/step_definitions/test_steps.rb

@@ -1,56 +0,0 @@
-require 'cucumber/rspec/doubles'
-
-RSPEC_EXPECTATION_NOT_MET_ERROR = RSpec::Expectations::ExpectationNotMetError
-
-Then /^the following steps? should (fail|succeed):$/ do |expectation, steps_table|
-  steps = steps_table.raw.flatten
-  
-  steps.each do |step|
-    if expectation == 'fail'
-      expect { step(step) }.to raise_error(RSPEC_EXPECTATION_NOT_MET_ERROR)
-    
-    else # succeed
-      step(step)
-    end
-
-  end
-end
-
-When /^I run the following steps?:$/ do |steps_table|
-  steps = steps_table.raw.flatten
-  
-  steps.each do |step|
-    step(step)
-  end
-end
-
-Then /^the following multiline step should (fail|succeed):$/ do |expectation, multiline_step|
-  multiline_step = multiline_step.gsub(%{'''}, %{"""})
-  if expectation == 'fail'
-    expect { steps(multiline_step) }.to raise_error(RSPEC_EXPECTATION_NOT_MET_ERROR)
-  else # succeed
-    steps(multiline_step)
-  end
-
-end
-
-Then(/^a hidden string with quotes should not be visible$/) do
-  hidden_string = %Q{hidden '" quotes}
-  assert_hidden(:text => hidden_string)
-end
-
-Then(/^a visible string with quotes should be visible$/) do
-  visible_string = %Q{visible '" quotes}
-  assert_visible(:text => visible_string)
-end
-
-Then(/^'show me the page' should open the page or take a screenshot$/) do
-  # Projects with Capybara 1 & 2 use the launchy gem
-  if Spreewald::Comparison.compare_versions(Capybara::VERSION, :<, "3.0")
-    expect(Launchy).to receive(:open)
-    step 'show me the page'
-  else
-    expect_any_instance_of(Capybara::Screenshot::Saver).to receive(:save)
-    step 'show me the page'
-  end
-end

data/tests/rails-4_capybara-3/features/support/paths.rb

@@ -1,16 +0,0 @@
-module NavigationHelpers
-  
-  def path_to(page_name)
-    case page_name
-    when /^"(.*)"$/
-      $1
-
-    else
-      raise "Can't find mapping from \"#{page_name}\" to a path.\n" +
-        "Now, go and add a mapping in #{__FILE__}"
-    end
-  end
-  
-end
-
-World(NavigationHelpers)

data/tests/rails-4_capybara-3/features/support/selectors.rb

@@ -1,52 +0,0 @@
-module HtmlSelectorsHelpers
-  # Maps a name to a selector. Used primarily by the
-  #
-  #   When /^(.+) within (.+)$/ do |step, scope|
-  #
-  # step definitions in web_steps.rb
-  #
-  def selector_for(locator)
-    case locator
-
-    when /^a panel?$/
-      '.panel'
-
-    when /^a panels nested contents?$/
-      '.panel--nested-contents'
-
-    when /^the timeline?$/
-      '.timeline'
-
-    when /^the table row containing "(.+?)"$/
-      all('tr').detect { |tr| tr.text.include? $1 } || raise("Could not find tr containing #{$1.inspect}")
-
-    when /^a table$/
-      '.table'
-
-      # Add more mappings here.
-      # Here is an example that pulls values out of the Regexp:
-      #
-      #  when /^the (notice|error|info) flash$/
-      #    ".flash.#{$1}"
-
-      # You can also return an array to use a different selector
-      # type, like:
-      #
-      #  when /the header/
-      #    [:xpath, "//header"]
-
-      # This allows you to provide a quoted selector as the scope
-      # for "within" steps as was previously the default for the
-      # web steps:
-    when /^"(.+)"$/
-      $1
-
-    else
-      raise "Can't find mapping from \"#{locator}\" to a selector.\n" +
-              "Now, go and add a mapping in #{__FILE__}"
-    end
-  end
-
-end
-
-World(HtmlSelectorsHelpers)